From: Albert C. <rub...@ml...> - 2006-11-02 05:44:39
|
On Tue, Oct 31, 2006 at 12:12:40AM -0600, Albert Chin wrote: > On Sat, Apr 22, 2006 at 07:49:15PM +0100, Jeremy Henty wrote: > > On Fri, Apr 21, 2006 at 06:22:26AM -0500, Albert Chin wrote: > > > > > That's why we need a way to explicitly set the C++ compiler > > > > If the attached extconf.rb doesn't work, can you send me your system's > > versions of rbconfig.rb and mkmf.rb , plus the Makefile and mkmf.rb > > created by "ruby extconf.rb"? Also, can you confirm that running > > "fltk-config --cxx" on the command line prints the name of the correct > > C++ compiler? If it does then extconf.rb will be able to determine > > the right compiler automatically and I won't need to add a build flag. > > Sorry for dropping this. I just tried 0.9.5 and the problem still > exists. I've attached copies of rbconfig.rb and mkmf.rb. Because "ruby > extconf.rb" fails (the conftest.cxx files are compiled with the C > compiler so all tests fail), no Makefile/mkmf.rb are created. > > $ fltk-config --cxx > CC > > I'm going to poke around in Ruby's mkmf.rb and try to figure this out. I have things working but I had to make changes to rbconfig.rb and mkmf.rb so I'll need to work these out with the Ruby folks. -- albert chin (ch...@th...) |