X-Authentication-Warning: delorie.com: mailnull set sender to djgpp-workers-bounces using -f
Date: Mon, 22 Apr 2002 22:26:13 +0100
From: Laurynas Biveinis <lauras AT softhome DOT net>
X-Mailer: The Bat! (v1.60c) Personal
X-Priority: 3 (Normal)
Message-ID: <1313279054.20020422222613@softhome.net>
To: "Tim Van Holder" <tim DOT van DOT holder AT pandora DOT be>
CC: bug-autoconf AT gnu DOT org, djgpp-workers AT delorie DOT com,
   "'Akim Demaille'" <akim AT epita DOT fr>
Subject: Re[3]: AC_PROG_CXX does not work correctly after AC_PROG_CC
In-Reply-To: <000d01c1ea1b$e9bd2bf0$918ce0d5@zastaixp>
References: <000d01c1ea1b$e9bd2bf0$918ce0d5 AT zastaixp>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 22 Apr 2002 20:23:24.0826 (UTC) FILETIME=[8DEE4FA0:01C1EA3B]
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


> My suggestion would probably be to
>   a) have the EXEEXT tests fail graciously (i.e. have them
>      give a 'warning: cannot determine executable extension
>      using the <LANG> compiler', and not set any findings (so
>      possible following AC_PROG_<COMPILER> calls can find it
>      out properly).

Why? EXEEXT works like a sanity check for a compiler.  As I understand
it, it bombs only if it cannot find an executable made by compiler.

>   b) have the AC_PROG_<compiler> either bomb out if the
>      requested compiler is not available, or set the respective
>      variable to 'none', so scripts can decide what to do.

I've seen in mailing list archives that this feature (making checks
optionals by user) was already considered couple of years ago,
however, there are still no signs of actual implementation.

Laurynas