Rob Biedenharn wrote: > Perhaps define LIBRARY_PATH in your environment? I can't remember if > there is a pure ruby adapter for MySQL (I presume that your problem is > during the build of the native component).
I'm not sure what you mean by "pure ruby adapter." There is supposedly a built-in adapter, but notes in AWDwR suggest that it's incomplete. Yes, the problem comes during the build of the native component. The mkmf.log file that's being left behind has several errors in it, but the predominant error is the linker being unable to find the mysqlclient library. The rest seem related to that (missing function calls, etc.) No joy on setting LIBRARY_PATH or LD_LIBRARY_PATH, I'm afraid. I find it a bit odd that there's no command line option to pass build arguments down to the compile of the native component. I suppose if I really wanted to make it happen this way I could build my own gem... but it might just be easier to rip out Locomotive and do a fully manual install of ruby/rails. I went with it originally because my package manager (Fink) is now using Rails 2.0.2 which is even less compatible with the book's instructions, but if Loco is going to cause me this much trouble, it's not worth it. Thanks again for all your help Rob! We may not have got Locomotive working, but I ended up with a far, far better understanding of what's happening with all the little components than I expected to have at this point in learning Ruby. :) Cheers, Matt -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
