[vsipl++] Re: overriding autoconf's own exeext detection

Stefan Seefeld stefan at codesourcery.com
Sat Nov 12 15:24:39 UTC 2005


Ralf Wildenhues wrote:
> Hi Stefan,
> 
> * Stefan Seefeld wrote on Fri, Nov 11, 2005 at 06:08:29PM CET:
> 
>>Ralf Wildenhues wrote:
>>
>>
>>>Does the patch below fix it?
>>
>>It looks good, though there is at least one more extension: '.inf',
>>which is generated with optimization. Other files with extensions
>>'.dbo', '.dla', etc. are created when object files are produces,
>>but these don't seem to confuse configure.
> 
> 
> I believe we do not need to add the other extensions (except for .inf)
> to _AC_COMPILER_OBJEXT_REJECT, unless the compiler uses neither `.o' nor
> `.obj' for object.  `configure' *should* in fact remove the other files
> created during its tests.

The default object extension for that compiler is '.oppc', fwiw.

[...]

>>Also, if I want to avoid upgrading autoconf, is there a way
>>to fix the problem locally, say, in my aclocal.m4 file ?
> 
> 
> Not that I know of.  You can always define your own macro, for example
> a fixed version with the same name.  But that may be very fragile, not
> compatible with the next or previous Autoconf, or anything, so I would
> not recommend it.  Maybe AC_EXEEXT should offer a possibility to
> override it.

AC_EXEEXT is marked as obsolete, as autoconf detects the extension 'automatically'.
Oh well. It might have been better if autoconf, recognizing its limitations, would
keep a backdoor for developers to override settings instead of forcing them to live
with false guesses.

> Updated patch below.

Ok, that seems to work. Thanks !

Regards,
		Stefan



More information about the vsipl++ mailing list