> > /usr/lib/ruby/gems/1.8/gems/mysql-2.7.3-mswin32/ext $ > cygcheck mysql.so > > Error: could not find mysql.so > > cygcheck is designed to check things on the PATH just as you would if > you were invoking a command, so unless you have . in PATH it isn't > expected to find anything in the PWD.
Hmmmm..... But I do have . in the PATH - at the very end: $ echo $PATH /cygdrive/h/bin:/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin:/cygdrive/c/ Tcl/bin:/cygdrive/c/Programme/Java/jdk1.5.0_11/bin:/cygdrive/h/winbin:/c ygdrive/h/jruby-0.9.9/bin:/cygdrive/c/ruby185/bin:/cygdrive/c/Python24/: /cygdrive/c/Perl/bin/:/cygdrive/c/WINDOWS/system32:/cygdrive/c/WINDOWS:/ cygdrive/c/WINDOWS/System32/Wbem:/cygdrive/c/Programme/Utimaco/SafeGuard Easy/:/cygdrive/c/Programme/jEdit:/cygdrive/c/Programme/MySQL/MySQL Server 5.0/bin:/cygdrive/c/WINDOWS/system32/WindowsPowerShell/v1.0:/cygdrive/c/ jakarta-jmeter-2.2/bin:. > 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. I understand! Thank you for the explanation. Ronald -- 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/
