[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Weird interactions between AC_PROG_CC and AC_PROG_F77

From: Stefano Lattarini
Subject: Re: Weird interactions between AC_PROG_CC and AC_PROG_F77
Date: Sat, 6 Feb 2010 18:56:32 +0100
User-agent: KMail/1.12.1 (Linux/2.6.30-2-686; KDE/4.3.2; i686; ; )

At Saturday 06 February 2010, Ralf Wildenhues <address@hidden> wrote:
> Hello Stefano,
Hello Ralf.  Thanks for your quick answer.

> * Stefano Lattarini wrote on Sat, Feb 06, 2010 at 04:14:45PM CET:
> > I encountered the following strage behaviour in the latest stable
> > autoconf (2.65, Debian package version 2.65-2), and it really
> > seems a bug to me:
> Of the AC_PROG_{CC,CXX,F77,FC} macros, only the first one in the
> configure script will check for object file extension and default
> executable file name and fail if that doesn't work.
Oh... I didn't know that.  Thanks for the information.

> If you need to know whether any of the compilers work, then you
>  need to add a compile, link, or run test to find out.  This may
>  seem surprising, and I bet it's not documented well enough,
IMHO it's not.  I think that a remark about this behaviour should be added at
the beginning of the Section 5.10 "Compilers and Preprocessors" (by the way,
the exact remark you made above seems fit for inclusion, as it's short while
also being quite clear).  I might try to write a simple patch tomorrow, but be
warned that I don't know texinfo at all, so the result might be suboptimal.
>  also I think we probably cannot fix it without breaking
>  bugward^Wbackward compatibility. 
Too bad :-(
Doesn't Autoconf have a way to introduce non-backward-compatible behaviours
through proper options, similar to e.g. Automake's `parallel-tests'?


reply via email to

[Prev in Thread] Current Thread [Next in Thread]