[Top][All Lists]

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

overriding autoconf's own exeext detection

From: Stefan Seefeld
Subject: overriding autoconf's own exeext detection
Date: Fri, 11 Nov 2005 09:31:18 -0500
User-agent: Mozilla Thunderbird 0.9 (X11/20041127)

I'm using autoconf with a greenhills cross-compiler.
It compiles source code into .ppc executables, but
generates auxiliary files with other extensions on-the-fly
(.map, for example).

Unfortunately, the way autoconf detects a compiler's
default executable extension is by making some guesses,
and eventually picking up the first extension not listed
in an exclusion list. Thus, in my case, configure thinks
that '' is the name of the executable, which leads
to failures later on.

Is there any way around this ? For my own build system
I added options --with-obj-exe and --with-exe-ext, but
those obviously don't affect tests run by configure

From a look into the relevant code it seems it would be
possible to fix this by adding some extensions to the
exclusion list, though I'm not sure how robust / scalable
a solution that is.

Any help is greatly appreciated !


reply via email to

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