overriding autoconf's own exeext detection

[Stefan Seefeld]

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 'test.map' 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
internally.

 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 !

Thanks,
		Stefan