On 18 Dec 2009, at 20:08, Ben Abbott wrote: > > Looks like I'm stuck. I need a gcc which includes gfortran and I > need fltk to build Octave ...
I don't think they have changed the compiler ABI at all between variants, well, not in the gcc 4.x series, have they? I know we had a world of pain moving from 2 to 3, and at several points in the gcc 3 series, but the gcc 4 C++ ABI is fixed now, I thought? Anyway, what I'm saying is: if you need to use two different compilers, then just use them. The generated .o files will have compatible ABI and you can then just link 'em all together. OSX (well Xcode) distributes with several gcc variants by default and has reasonable mechanisms for keeping them apart, and it all seems to work OK. So use an Apple gcc for your GUI / fltk / whatever work, and your other compiler for your gfortran sources or whatever, then just hope for the best. Worth a shot, at any rate. > hmmm, perhaps the only solution is to enable x11 (disable quartz) > with fltk-1.1.9? No, I don't think that works with the 1.1.x series. It was supported briefly while the initial OSX porting work was done, but was later deprecated. Oddly, I have a vague recollection that it fixed up again for fltk-1.3... but I think we have already established that isn't looking to positive for you with your later gcc yet! -- Ian _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
