RE: [Flightgear-devel] Building FlightGear / getting some errors
Yes, it fails with exit Error: The input line is too long. I was going to look into this a bit more but the real world is calling quite loudly at the moment. Is there anybody who has successfully built fgfs under mingw32? And does anybody know what I need to do to cull the UIUC and LARCsim files from the codebase in order to reduce the input length? Giles Robertson PS: I can't really give you much hard data until sometime later this week, unfortunately. -Original Message- From: Andy Ross [mailto:[EMAIL PROTECTED] Sent: 19 April 2004 21:07 To: FlightGear developers discussions Subject: Re: [Flightgear-devel] Building FlightGear / getting some errors Giles Robertson wrote: Not that I've noticed. It would be useful for mingw32. I've tried building on that, and it compiles fine, but the linker fails because the input is too long ;). The linker fails with long file lists? That sounds odd -- this is the same linker used in Linux, and it's always been quite robust in my experience. Are you sure you aren't simply running out of memory or swap? The final fgfs link is definitely memory-intensive. Andy ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] Building FlightGear / getting some errors
Ah. Thanks. I'll try that. I was hoping to try and get along with something slightly less stodgy than Cygwin, though. I was also hoping to use MSYS so that I didn't need to use Cygwin or a windows IDE to produce the makefile. I've always thought that Cygwin was a little heavy for something that should be quite simple :) Giles -Original Message- From: Norman Vine [mailto:[EMAIL PROTECTED] Sent: 19 April 2004 21:28 To: FlightGear developers discussions Subject: RE: [Flightgear-devel] Building FlightGear / getting some errors Andy Ross writes: Giles Robertson wrote: Not that I've noticed. It would be useful for mingw32. I've tried building on that, and it compiles fine, but the linker fails because the input is too long ;). The linker fails with long file lists? That sounds odd -- The Windows cmd shell has a command line length limitation that I get around by using MingW from a Cygwin bash shell. Compiling from a bash shell under MSYS might work too I don't really know as I haven't used it Note when using bash under Cygwin you need to substitute the Cygwin 'make' for the MingW 'make' and you will need to configure using the appropriate --prefix argument for your system Perhaps the easiest way around this is to use the standard way of overcoming the Windows command line length limitation by redirecting the link command line to a file and then massaging that so as to have the final linking arguments to gcc be read from that file I believe that this could be done using the --dry-run flag for make but I have nevered tried this as I use a Cygwin shell as outlined above HTH Norman ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] Building FlightGear / getting some errors
Hi Giles Giles Robertson writes Ah. Thanks. I'll try that. I was hoping to try and get along with something slightly less stodgy than Cygwin, though. I was also hoping to use MSYS so that I didn't need to use Cygwin or a windows IDE to produce the makefile. I've always thought that Cygwin was a little heavy for something that should be quite simple :) With ref MSYS I tried this about two weeks back but the MSYS shell does not have a USR directory which means Simgear can't find Plib.If you are interested I asked over on the MSYS list about two weeks ago. But the answers went right over my head.But from what I could gather it cant be done.But you might beable to make more sense of it. Cheers Innis Giles _ Personalise your phone with chart ringtones and polyphonics. Go to http://ringtones.com.au/ninemsn/control?page=/ninemsn/main.jsp ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] Building FlightGear / getting some errors
Innis Cunningham writes: Giles Robertson writes Ah. Thanks. I'll try that. I was hoping to try and get along with something slightly less stodgy than Cygwin, though. I was also hoping to use MSYS so that I didn't need to use Cygwin or a windows IDE to produce the makefile. I've always thought that Cygwin was a little heavy for something that should be quite simple :) With ref MSYS I tried this about two weeks back but the MSYS shell does not have a USR directory which means Simgear can't find Plib.If you are interested I asked over on the MSYS list about two weeks ago. But the answers went right over my head.But from what I could gather it cant be done.But you might beable to make more sense of it. You should be able to mount a /usr directory in MSYS but even if you can't you can always instal PLib to a different directory i.e use the configure --prefix argument or by using the make install prefix=XX construct HTH Norman ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Building FlightGear / getting some errors
Jon S. Berndt wrote: undefined reference to `___gxx_personality_v0' undefined reference to `__Unwind_Resume' ... Those are internal g++ things. It looks like you upgraded your compiler without doing a full rebuild? Versions of g++ are not binary-compatible between versions*. Andy * Well, since gcc 3.2.x they are using a standard ABI that they promise will not change. We'll see how that plays out. :) ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Building FlightGear / getting some errors
On Mon, 19 Apr 2004 07:11:26 -0700 Andy Ross [EMAIL PROTECTED] wrote: Jon S. Berndt wrote: undefined reference to `___gxx_personality_v0' undefined reference to `__Unwind_Resume' ... Those are internal g++ things. It looks like you upgraded your compiler without doing a full rebuild? Versions of g++ are not binary-compatible between versions*. Yeah, it was my mistake. I think what happened is that I upgraded parts of my CygWin installation in a bad way. When I uninstalled automake and autoconf, then reinstalled them cleanly, then did a make clean, and a complete rebuild of all the parts of FlightGear, things came out a lot nicer. I'm still not getting a full rebuild, but that's because of the recent JSBSim reorg and the Makefile changes that will need to be worked out, which hasn't been done yet. Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] Building FlightGear / getting some errors
2) For an FDM developer, how can some of the FDMs be left out of the build if a developer is only concentrating on development of one FDM? Is this easily possible? Not that I've noticed. It would be useful for mingw32. I've tried building on that, and it compiles fine, but the linker fails because the input is too long ;). I've also tried cutting out file-expensive FDMs (read: UIUC LARCsim), but that doesn't do the rest of the compile any good. I'll have another look into it when I've passed my current work crisis (huge). Giles Robertson ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Building FlightGear / getting some errors
Giles Robertson wrote: Not that I've noticed. It would be useful for mingw32. I've tried building on that, and it compiles fine, but the linker fails because the input is too long ;). The linker fails with long file lists? That sounds odd -- this is the same linker used in Linux, and it's always been quite robust in my experience. Are you sure you aren't simply running out of memory or swap? The final fgfs link is definitely memory-intensive. Andy ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] Building FlightGear / getting some errors
Andy Ross writes: Giles Robertson wrote: Not that I've noticed. It would be useful for mingw32. I've tried building on that, and it compiles fine, but the linker fails because the input is too long ;). The linker fails with long file lists? That sounds odd -- The Windows cmd shell has a command line length limitation that I get around by using MingW from a Cygwin bash shell. Compiling from a bash shell under MSYS might work too I don't really know as I haven't used it Note when using bash under Cygwin you need to substitute the Cygwin 'make' for the MingW 'make' and you will need to configure using the appropriate --prefix argument for your system Perhaps the easiest way around this is to use the standard way of overcoming the Windows command line length limitation by redirecting the link command line to a file and then massaging that so as to have the final linking arguments to gcc be read from that file I believe that this could be done using the --dry-run flag for make but I have nevered tried this as I use a Cygwin shell as outlined above HTH Norman ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] Building FlightGear / getting some errors
Jon Berndt writes: When building FlightGear (and my setup in CygWin is now building plib and SimGear just fine), when I get to the YASim directory, I get these errors: g++ -D_REENTRANT -L/usr/local/lib -o yasim.exe yasim-test.o Airplane.o Atmosphere.o ControlMap.o FGFDM.o Gear.o Glue.o Integrator.o Jet.o Math.o Model.o PistonEngine.o PropEngine.o Propeller.o RigidBody.o Rotor.o Rotorblade.o Rotorpart.o SimpleJet.o Surface.o Thruster.o Wing.o Turbulence.o -lsgxml -lsgprops -lsgmisc -lsgdebug -lsgstructure Atmosphere.o(.eh_frame+0x11):Atmosphere.cpp: undefined reference to `___gxx_personality_v0' ControlMap.o(.text+0x1db):ControlMap.cpp: undefined reference to `__Unwind_Resume' ControlMap.o(.text+0x34e):ControlMap.cpp: undefined reference to `__Unwind_Resume' ControlMap.o(.eh_frame+0x12):ControlMap.cpp: undefined reference to `___gxx_personality_v0' Gear.o(.eh_frame+0x11):Gear.cpp: undefined reference to `___gxx_personality_v0' ... etc. 1) Did I do something stupid to my build setup again? :-) My guess is that you did a MingW build in the same directory and did not do a mkae clean. This is why the recomended way of building a project with the GNU auto tools is to configue and build in a separate directory for each system i.e % cd $PROJ_TOP % aclocal; autoconf; automake % mkdir cygwin % cd cygwin % ../configure $CYGWIN_ARGS; make; make install % cd .. % mkdir MingW % cd MingW % ../configure $MINGW_ARGS; make; make install and your projects will not conflict with one another as long as you use an appropriate --prefix arg to configure :-) Note the same trick is useful when using a cross compiler in Linux HTH Norman ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
