Autoconf 2.69 and mingw

Chris Johns chrisj at
Fri Mar 22 22:34:30 UTC 2013

Peter Dufault wrote:
> On Mar 21, 2013, at 17:01 , Chris Johns<chrisj at>  wrote:
>> This is cross-built and if it works it is by luck and not design. I now
>> always build it from source on each host platform I use.
> I don't like needing to build on the host platform, since host != build != target.
> I want to be able to always build everything on "build".  If you need to build on "host", and in the field you have some requirement to run tools on a mingw "host" that is old and cranky and you need to update those tools, I'd rather not need to dig up the old cranky mingw to do the build of the "host" tools.

For binutils, gcc etc this is reasonable and possible, for autoconf it 
is not. For me I would use a suitable host to build the tools and then I 
would take the generated tar files that I have tested to the other host 
machine and install. I would not take into the field something I have 
not first tested in my lab environment.

> I think it's important to build everything on "build".

You would need to take this up with the autoconf people.


More information about the devel mailing list