>> Main problem with autoconf is the performance hit for native builds.
>
>How much of a performance hit? I don't really see this here.

On a 2-3GHz x86, it isn't much of a hit.  On a 40MHz sparc (or worse)
it can be significant - and these are the platforms least likely
to be doing cross-builds.

>> I think I've mentioned before that that could be addressed with some
>> suitable make fu - ie. if we're not cross-building, add a -Inative/include
>> or something (where you have static versions of headers suitable for 
>> native builds), else run configure - probably want an autoconf.mk
>> 
>> I've never seen any indication though that others want the above,
>> so never set it up.
>> 
>
>Which include though? 

Typically config.h as in

#ifdef HAVE_CONFIG_H
# include <config.h>
#endif

>We can't depend on the system includes even if native
>since they're not necessarily in-sync with what's in the build you're 
>attempting to complete.

But then you are cross-building, and autoconf is appropriate.

--sjg