On Jun 18 06:19, Brian Dessent wrote: > Ronald Fischer wrote: > > > There is none. I was told by Ruby-Talk people that I should use the > > Windows > > gem - it would work fine. > > Ugh.
Indeed, ugh. Who told you that, some random guy on ruby-talk or somebody who actually knows what (s)he's talking about? > You're mixing native win32 stuff with Cygwin stuff. You're trying to > load the module into a running copy of a Cygwin ruby but this module > imports symbols from the other copy of ruby in in C:\ruby185\. This > means it probably expects data structures of the native build, and most > likely will crash or act with very unpredictable behavior when used > elsewhere. In general this kind of cross-polination is never a good > idea. > > The *right* way to do it is to either stick to the win32 build (only) or > to build all the components that you want to use as Cygwin modules. Exactly. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
