On Oct 31, 2009, at 1:58 , Nic Benders wrote: > You want to look in the gem extension's build directory for the actual > output file from "configure". When it is testing something like > "looking for mysql.h", what it is really doing is trying to compile a > very simple C program that uses "include <mysql.h>" or equivalent. > Although the "configure" program only outputs yes or no when it is > run, it will also generally leave a log with the actual compiler > error, and possibly the test code and command. With that you can > figure out if the Ruby setup is at fault, or if you have some other, > possibly unrelated compiler issue.
Many thanks for your help. But please define "the gem extension's build directory" and how I determine what that is. --~--~---------~--~----~------------~-------~--~----~ SD Ruby mailing list [email protected] http://groups.google.com/group/sdruby -~----------~----~----~----~------~----~------~--~---
