Re: [gnu.utils.bug] AC_PROG_CC_G, et al, are not very robust

[Mo DeJong]

On 14 Jun 2000, Akim Demaille wrote:

> >>>>> "Alexandre" == Alexandre Oliva <[EMAIL PROTECTED]> writes:
> 
> Alexandre> Because some compilers just print a warning message and
> Alexandre> proceed.  GCC on HP/UX without GNU as is a good example.
... 
> So, I think we should base our conclusion upon conftest.o, not
> stderr+stdout.


Perhaps this is a silly idea, but why don't you just run the compiler
without the -g flag to make sure that it created a conftest.o file,
and then run with the -g flag but check that the produced conftest.o
is larger than the first one. If -g adds debug info to conftest.o
then it is going to get bigger. If -g is not known to the compiler,
it should produce a .o file that is exactly the same size. That
way you could avoid all the stdio+stderr junk.

Mo DeJong
Red Hat Inc.