Re: configure sets CFLAGS or how to disable default CFLAGS='-g -O2' for gcc?

2006-04-05 Thread Chris Pickett
Ralf Wildenhues wrote: * Chris Pickett wrote on Wed, Apr 05, 2006 at 07:28:23AM CEST: For example, I didn't know AC_PROG_CC set "-g -O2", even though I had been using it for a while. Quoting info Autoconf "C Compiler": | If using the GNU C compiler, set shell variable `GCC' to `yes'. | If

Re: configure sets CFLAGS or how to disable default CFLAGS='-g -O2' for gcc?

2006-04-05 Thread Ralf Wildenhues
Please accept my apologies if you feel I'm beating a dead horse. * Chris Pickett wrote on Wed, Apr 05, 2006 at 09:03:28AM CEST: > Ralf Wildenhues wrote: > >* Chris Pickett wrote on Wed, Apr 05, 2006 at 07:28:23AM CEST: > > > >>For example, I didn't know AC_PROG_CC set "-g -O2", even > >>though I

Re: Subject: [GNU Autoconf 2.59] testsuite: 40 41 51 183 failed

2006-04-05 Thread Ralf Wildenhues
Hi John, * John L. Ries wrote on Wed, Apr 05, 2006 at 01:51:06AM CEST: > The Autoconf in question was built on a DEC 3000/600 under Tru64 UNIX 5.0 > with GNU m4 1.4, Perl v5.8.6, and gawk 3.0.4. Please let me know if you > need further information. Well, it would be great if you could redo tes

Autotesting - GNU Autoconf

2006-04-05 Thread Randima
Hi, When writing test suites in testsuite.at for autotesting I would like to know how to access the test file names. Do we need to give absolute file names for input test files? If so, migrating to another development enviornment would result test case failures. And what is the recommened way to

Re: Autotesting - GNU Autoconf

2006-04-05 Thread Ralf Wildenhues
Hi Randima, * Randima wrote on Thu, Apr 06, 2006 at 05:13:43AM CEST: > > When writing test suites in testsuite.at for autotesting I would like to > know how to access the test file names. > Do we need to give absolute file names for input test files? If so, > migrating to another development env