Re: gcc -nologo?

[Steven G. Johnson]

First, when reporting a potential bug, you should try to give some
relevant information, such as the operating system you are using, the CPU,
the compiler version, and so on.  (A minimal configure.in that exhibits
the problem would also be useful, if you can make one.)

Second, you should try the latest snapshot of autoconf
(ftp://alpha.gnu.org/pub/gnu/autoconf/autoconf-2.49d.tar.gz) to see if it
continues to exhibit a similar problem.  (It shouldn't give exactly the
same error, because the new version no longer tries the -nologo flag.  
But I don't see why you should ever see that in your case, either, since
it sounds like you are using a Debian Linux system.)  (If you don't want
to touch the autoconf on your system, just install it in your home
directory with './configure --prefix=$HOME/testing' or something like
that.)

Third, it seems to be incorrectly figuring out how to run the C
preprocessor.  To do this, autoconf-2.13 tries to preprocess a small file
containing two lines:

#include <assert.h>
Syntax Error

(The second line is to give an error if it tries to compile it, I think.)
It first tries 'gcc -E', then 'gcc -E -traditional-cpp', then 'gcc -nologo
-E', then some other things.  You might try running these tests "by hand"
to see if they work, or if there is something broken on your system.

A workaround, by the way, should be to set the CPP environment variable to
the name of a working C preprocessor command on your system.

Cordially,
Steven G. Johnson