> From: Arthur Wiebe <[EMAIL PROTECTED]> > Reply-To: FlightGear developers discussions <[EMAIL PROTECTED]> > Date: Thu, 11 Nov 2004 13:41:58 -0500 > To: FlightGear developers discussions <[EMAIL PROTECTED]> > Subject: Re: [Flightgear-devel] Re: FlightGear on Mac OS X > > After setting two environment variables I was able to get simgear > 0.3.7 to compile without any problems. > > In bash you would set them like this: > export CFLAGS=-I/usr/X11R6/include > export CXXFLAGS=-I/usr/X11R6/include > > And I built plib 1.8.3 with help from the diffs you sent but building > from CVS worked for me without any patching.
I guess that means that the appropriate patches are already in the plib CVS, just not yet released. > > Now FlightGear itself is another story. I had to upgrade automake in > order to run the autogen.sh script successfully. That is very strange, because I did not have to. I wonder what is different about our setups? > > I have not yet got FlightGear 0.9.6 to compile. Keep on getting: > > -lplibfnt -lplibul -framework GLUT -framework OpenGL -framework AGL > -framework Carbon -lobjc > ld: Undefined symbols: > fntTexFont::load(char const*, unsigned int, unsigned int) > make[2]: *** [layout-test] Error 1 > make[1]: *** [all-recursive] Error 1 > make: *** [all-recursive] Error 1 What is also strange is that I can get FG to compile, up to the final link stage. I think that is the same problem that you are having, but we are getting different Undefined symbols. Mine seem to be from stuff that I have already built (plib). > > I will now try to get FlightGear from CVS to build. Not that I think > it will work. > > On Thu, 11 Nov 2004 10:24:45 -0800, Adam Dershowitz > <[EMAIL PROTECTED]> wrote: >> And were you able to get it all to build fine without any patches? >> As I said in the other Mac OS X thread, I had to make a few changes to get >> plib and SimGear to compile. >> And then I got it all to compile but the final link of FlightGear fails with >> some undefined symbols. These are things that should be in the library >> files that were already built. >> >> I am using gcc 3.3, automake 1.6.3 and autoconf 2.53 (these are the >> standards that are included with Xcode 1.5). And all fresh CVS code. >> >> -- Adam >> >>> From: <[EMAIL PROTECTED]> >>> Reply-To: FlightGear developers discussions >>> <[EMAIL PROTECTED]> >>> Date: Thu, 11 Nov 2004 12:22:52 -0500 >>> To: <[EMAIL PROTECTED]> >>> Subject: [Flightgear-devel] Re: FlightGear on Mac OS X >> >> >>> >>> Arthur, >>> >>> Makefile.in isn't in CVS. It is generated by automake. >>> >>> GNU Automake - http://www.gnu.org/software/automake >>> Freeware - Generates makefile.in files from makefile.am input files, >>> as part of the official GNU coding standards and build process. >>> Requires GNU autoconf. >>> On Nov 11, 2004, at 9:52 AM, [EMAIL PROTECTED] >>> wrote: >>> >>> are you running ./autogen.sh without an errors? Have you updated >>> aclocal and autoconf also? >>> >>> I just did a make clean and a plib build from cvs and it worked fine >>> under Mac os X (10.6). The rest of the build went ok also (simgear and >>> flightgear) though I had a modified (flightgear) Input/input.cxx and >>> Main/options.cxx. The FlightGear changes are for debugging some things >>> I was looking at at one time... >>> >>> I'm doing a 'make clean install' for SimGear and FlightGear now from >>> latest (1700 GMT) cvs. My plib and simgear are straight from cvs, >>> flightgear and data are straight from cvs (no modified local copies, >>> except for the FlightGear input.cxx and options.cxx files that I >>> mentioned above). >>> >>> Ima >>> >>>> >>>> Message: 8 >>>> Date: Thu, 11 Nov 2004 09:51:09 -0500 >>>> From: Arthur Wiebe <[EMAIL PROTECTED]> >>>> Subject: Re: [Flightgear-devel] Re: FlightGear on Mac OS X >>>> To: FlightGear developers discussions >>>> <[EMAIL PROTECTED]> >>>> Message-ID: <[EMAIL PROTECTED]> >>>> Content-Type: text/plain; charset=US-ASCII >>>> >>>> Since I was getting nowhere trying to build FG 0.9.6 I checked it out >>>> from CVS instead. After getting automake 1.9.3 I was able to run >>>> autogen.sh and configure but it seems Makefile.in is missing in CVS. >>>> >>>> configure: creating ./config.status >>>> config.status: creating Makefile >>>> config.status: error: cannot find input file: Makefile.in >>>> >>>> That seems hard to believe though although it's true. I have no >>>> Makefile.in. >>> >>> >>> _______________________________________________ >>> Flightgear-devel mailing list >>> [EMAIL PROTECTED] >>> http://mail.flightgear.org/mailman/listinfo/flightgear-devel >>> 2f585eeea02e2c79d7b1d8c4963bae2d >> >> _______________________________________________ >> Flightgear-devel mailing list >> [EMAIL PROTECTED] >> http://mail.flightgear.org/mailman/listinfo/flightgear-devel >> 2f585eeea02e2c79d7b1d8c4963bae2d >> > > > -- > <Arthur/> > > _______________________________________________ > Flightgear-devel mailing list > [EMAIL PROTECTED] > http://mail.flightgear.org/mailman/listinfo/flightgear-devel > 2f585eeea02e2c79d7b1d8c4963bae2d _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
