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. On Wed, 10 Nov 2004 18:26:04 -0500, Arthur Wiebe <[EMAIL PROTECTED]> wrote: > I have built PLIB 1.8.3 and SimGear 0.3.7. > But building FlightGear 0.9.6 has not yet been successful. > > I used ./configure --prefix=$BUILDDIR --without-x > and then plain make. > It looked like everything was going to work until... here's a cut of > the output leading up to the error: > > if g++ -DHAVE_CONFIG_H -I. -I. -I../../src/Include -I../.. -I../../src > -I/fgfs/include -I/usr/X11R6/include -D_REENTRANT -MT puList.o -MD > -MP -MF ".deps/puList.Tpo" -c -o puList.o puList.cxx; \ > then mv -f ".deps/puList.Tpo" ".deps/puList.Po"; else rm -f > ".deps/puList.Tpo"; exit 1; fi > if g++ -DHAVE_CONFIG_H -I. -I. -I../../src/Include -I../.. -I../../src > -I/fgfs/include -I/usr/X11R6/include -D_REENTRANT -MT AirportList.o > -MD -MP -MF ".deps/AirportList.Tpo" -c -o AirportList.o > AirportList.cxx; \ > then mv -f ".deps/AirportList.Tpo" ".deps/AirportList.Po"; else rm -f > ".deps/AirportList.Tpo"; exit 1; fi > if g++ -DHAVE_CONFIG_H -I. -I. -I../../src/Include -I../.. -I../../src > -I/fgfs/include -I/usr/X11R6/include -D_REENTRANT -MT layout.o -MD > -MP -MF ".deps/layout.Tpo" -c -o layout.o layout.cxx; \ > then mv -f ".deps/layout.Tpo" ".deps/layout.Po"; else rm -f > ".deps/layout.Tpo"; exit 1; fi > if g++ -DHAVE_CONFIG_H -I. -I. -I../../src/Include -I../.. -I../../src > -I/fgfs/include -I/usr/X11R6/include -D_REENTRANT -MT layout-props.o > -MD -MP -MF ".deps/layout-props.Tpo" -c -o layout-props.o > layout-props.cxx; \ > then mv -f ".deps/layout-props.Tpo" ".deps/layout-props.Po"; else rm > -f ".deps/layout-props.Tpo"; exit 1; fi > rm -f libGUI.a > ar cru libGUI.a new_gui.o dialog.o menubar.o gui.o gui_funcs.o > gui_local.o mouse.o preset_dlg.o prop_picker.o sgVec3Slider.o > trackball.o puList.o AirportList.o layout.o layout-props.o > ranlib libGUI.a > if g++ -DHAVE_CONFIG_H -I. -I. -I../../src/Include -I../.. -I../../src > -I/fgfs/include -I/usr/X11R6/include -D_REENTRANT -MT layout-test.o > -MD -MP -MF ".deps/layout-test.Tpo" -c -o layout-test.o > layout-test.cxx; \ > then mv -f ".deps/layout-test.Tpo" ".deps/layout-test.Po"; else rm -f > ".deps/layout-test.Tpo"; exit 1; fi > g++ -I/usr/X11R6/include -D_REENTRANT -L/fgfs/lib -o layout-test > layout-test.o libGUI.a -lsgprops -lsgdebug -lsgstructure -lsgmisc > -lsgxml -lplibpw -lplibpu -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 > > Do you have any ideas or had this error yourself? > > By the way, Mac OS X packages of PLIB are at > http://awiebe.blogdns.net/download/PLIB/MacOSX/ > > Hoping to add a flightgear and simgear package as well soon. > > > > On Wed, 10 Nov 2004 16:03:39 -0500, [EMAIL PROTECTED] > <[EMAIL PROTECTED]> wrote: > > Arthur > > > > I'm glad plib built for you. I only put plib and other flightgear files > > in a local tree and use --prefix so configure can find them. Also that > > way, I don't have to worry about old versions of plib that might be on > > my system somewhere. > > > > if you use --prefix with a non-system directory, you can avoid having > > to use sudo make install for library installation also. > > > > Lots of people on the list have run into problems related to old(er) > > versions of libraries on their systems in multiple paths. I'm sure > > that I ran into this one before I started using --prefix > > > > On Nov 10, 2004, at 2:49 PM, Arthur wrote: > > > > > Date: Wed, 10 Nov 2004 14:49:32 -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 > > > > > > > > > > Well... I got simgear configured. > > > > > > Before I didn't specify --prefix for plib or simgear. Now I made a > > > directory called fgfs in / and install plib there and then specified > > > that plib was installed there when configuring simgear and used the > > > same prefix for simgear. Now it worked. > > > This leads me to thinking it was a crazy permissions problem! > > > > > > Well at least it works now and I will be making a Mac OS X installer > > > package for plib 1.8.3 and posting it online for other people like me. > > > > > > Next step is to get simgear and flightgear to compile. I guess you'll > > > hear from me again soon. > > > > > > > good luck! Use the same --prefix for plib, simgear and flightgear. Is > > everything building OK now? Remember you can't mix and match release > > and CVS versions, either release plib, simgear and flightgear source OR > > CVS plib, simgear, flightgear source. > > > > There is also talk on the list recently about file name collisions on > > case preserving but not case significant file systems (like cygwin and > > mac os x). You'll see this when you're downloading the data from cvs > > under mac os x, if you're using HFS+ as opposed to a *nix file system > > on your Mac with a few files unless they've been fixed already. > > > > Anyway you want CVS plib to have Olivier's great joystick fixes anyway. > > I'm not sure they're in a release yet. I use the CVS source tree, which > > a few times a year gets into a non-buildable state for a day or two but > > is not usually a problem. > > > > I don't have Mac os X installs for anything, but one of the other Mac > > people (Jonathan, perhaps?) had created a Mac os X cocoa executable for > > FGFS. I don't recall if they had an app for installation, however. I > > think it was just drag and drop. I don't know if this app has been > > updated. > > > > I'm assuming you no longer need ./lib/libplibXXX and ./include/plib > > sent to you? 8-) > > > > Have fun and please let the list know how it goes. > > > > Provided you've got the dependencies installed, the Mac OS X build goes > > just like any other *nix clone 8-). Hopefully, you'll have no build > > problems once you're using --prefix. Just remember to build flightgear > > using ./configure --without-x unless you want to use X11 on mac os x > > (which is NOT installed by default). > > > > There, I think that's all the mac related screwups, I've done 8-) > > > > Enjoy the world's best Mac OS X opensource flightsim... > > > > Now if someone would just do Washington, DC scenery for flightgear. I > > used to have a nice DC add-on for XPlane... > > > > Ima > > > > _______________________________________________ > > > > > > Flightgear-devel mailing list > > [EMAIL PROTECTED] > > http://mail.flightgear.org/mailman/listinfo/flightgear-devel > > 2f585eeea02e2c79d7b1d8c4963bae2d > > > > > -- > <Arthur/> > -- <Arthur/> _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
