X-Authentication-Warning: delorie.com: mailnull set sender to djgpp-workers-bounces using -f
From: "Tim Van Holder" <tim DOT van DOT holder AT pandora DOT be>
To: <djgpp-workers AT delorie DOT com>
Subject: RE: DJGPP-specific (?) bug in Autoconf 2.50
Date: Sat, 20 Apr 2002 11:25:10 +0200
Message-ID: <000701c1e84d$44a9d070$9b5f77d5@zastaixp>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.3416
In-reply-to: <172511444808.20020416221124@softhome.net>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
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

Sorry for the late response - I was in Germany on business for a week.

> Hello,
> 
> Suppose you have C but not C++ compiler installed. Now following
> configure.ac:
> ---
> AC_INIT(blabla, 0.1)
> 
> AC_PROG_CC
> AC_PROG_CXX
> 
> AC_OUTPUT
> ---
> will produce following output:
> ---
> [...]
> checking for gcc... gcc
> checking for C compiler default output... a.exe
> checking whether the C compiler works... yes
> checking whether we are cross compiling... no
> checking for executable suffix... .exe
> checking for object suffix... o
> checking whether we are using the GNU C compiler... yes
> checking whether gcc accepts -g... yes
> checking for g++... no
> [...]
> checking for xlC... no
> checking whether we are using the GNU C++ compiler... no
> checking whether g++ accepts -g... no
> configure: creating ./config.status
> ---
> Huh? It thinks that C++ compiler is available. I think AC_EXEEXT
> (or how it is called in 2.50?), or brain damage in AC_PROG_CXX
> is guilty: AC_PROG_CXX has only one way to check if C++ really
> works: AC_EXEEXT. However, if there is AC_PROG_CC before
> AC_PROG_CXX, it will call AC_EXEEXT first, and AC_PROG_CXX would do
> nothing in this case. Drat. I would take up this with Autoconf
> maintainers, but for that I would have to use latest autoconf version,
> which is not available for DJGPP. Any suggestions or am I missing
> something?

This seems to be fixed in current autoconves:

configure: loading site script /dev/env/DJDIR/share/config.site
checking for gcc... gcc
checking for C compiler default output... a.exe
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables... .exe
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for g++... no
checking for c++... no
checking for gpp... no
checking for aCC... no
checking for CC... no
checking for cxx... no
checking for cc++... no
checking for cl... no
checking for FCC... no
checking for KCC... no
checking for RCC... no
checking for xlC_r... no
checking for xlC... no
checking whether we are using the GNU C++ compiler... no
checking whether g++ accepts -g... no
configure: creating ./config.status

It does set CXX to g++ though - but I figure that's as good a
default value as any (it can't assume gcc can compile C++ code
since the typical C++ driver program isn't found).

Apparently 2.54 will be released quickly due to a few bugs;
hopefully I'll have the time to get rid of all current testsuite
failures on DJGPP by then.
If desired, I could upload a DJGPP package of 2.53 for the alpha
directory; note that this version will NOT work if you specify
a full DOS path (i.e. with drivespec) as source dir (though you
can easily use a /dev-style path as a workaround).