Re: [Flightgear-devel] Capturing warnings

2002-07-02 Thread julianfoad
Jonathan Polley wrote: Along the lines of adding the -pedantic option, I would like to add an ability (probably at ./configure time) to specify additional compile options. Since one of my platforms is a Mac, I would like to be able to add -wno_long_double, as it keeps telling me that

Re: [Flightgear-devel] Capturing warnings

2002-07-02 Thread Jonathan Polley
What I would prefer is something similar to --prefix=, so that I could just add to the list, rather than replacing it. I.e., ./configure --prefix=/sw --with-GL=/sw --add_switches=-wno_long_double this way I don't have to know what the current configuration is. Just a thought, Jonathan

Re: [Flightgear-devel] Capturing warnings

2002-07-02 Thread Curtis L. Olson
David Luff writes: Unfortunately, when ./configure gets run automatically after typing make, the configure switches after ./configure get remembered, but the flags in front of ./configure don't (this is using Cygwin Bash). Is there any way round this? I've been catching this situation

Re: [Flightgear-devel] Capturing warnings

2002-07-02 Thread julianfoad
Curtis L. Olson wrote: David Luff writes: Unfortunately, when ./configure gets run automatically after typing make, the configure switches after ./configure get remembered, but the flags in front of ./configure don't (this is using Cygwin Bash). Is there any way round this? I've

Re: [Flightgear-devel] Capturing warnings

2002-07-01 Thread Julian Foad
I now have a practical solution for saving the compiler warnings: a wrapper script replacement for the compiler. rm config.cache # Otherwise it keeps the previous values of CC and CXX. GCCFLAGS=-Wall -pedantic -Wpointer-arith CC=saveoutp gcc CXX=saveoutp c++ CFLAGS=$GCCFLAGS

Re: [Flightgear-devel] Capturing warnings

2002-07-01 Thread Jonathan Polley
Along the lines of adding the -pedantic option, I would like to add an ability (probably at ./configure time) to specify additional compile options. Since one of my platforms is a Mac, I would like to be able to add -wno_long_double, as it keeps telling me that their size is non-portable.

Re: [Flightgear-devel] Capturing warnings

2002-06-25 Thread James Turner
On Tuesday, June 25, 2002, at 01:31 am, Andy Ross wrote: Jonathan Polley wrote: I cannot redirect stderr via 'command 2 file' on my Mac, so the easy solution was out. I did find that the following command works: Rubbish. Sure you can. You just have to run a real shell. :) Seriously,

[Flightgear-devel] Capturing warnings

2002-06-24 Thread Julian Foad
Making all in Main c++ -DHAVE_CONFIG_H -I. -I. -I../../src/Include -I../.. -I../../src -I/usr/local/include -DPKGLIBDIR=\/usr/local/lib/FlightGear\ -g -O1 -finline-limit-6 -finline-functions -Wall -pedantic -Wpointer-arith -c main.cxx main.cxx: In function `void fgUpdateTimeDepCalcs()':

Re: [Flightgear-devel] Capturing warnings

2002-06-24 Thread Jonathan Polley
I cannot redirect stderr via 'command 2 file' on my Mac, so the easy solution was out. I did find that the following command works: (make /dev/null) make.txt The reason for this can be found at: http://www.faqs.org/faqs/unix-faq/faq/part2/section-9.html I don't know if this will work on

Re: [Flightgear-devel] Capturing warnings

2002-06-24 Thread Andy Ross
Jonathan Polley wrote: I cannot redirect stderr via 'command 2 file' on my Mac, so the easy solution was out. I did find that the following command works: Rubbish. Sure you can. You just have to run a real shell. :) Basically, this is a long-standing misfeature of csh, which never existed