Autoconf 2.69 and mingw

Peter Dufault dufault at
Fri Mar 22 22:40:53 UTC 2013

On Mar 22, 2013, at 18:34 , Chris Johns <chrisj at> wrote:

> 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.

It's probably mostly "objdump" and friends that one needs in the field.  And they probably don't need to be updated.  I need to look at the autoconf issues you refer to before I comment further.

Peter Dufault
HD Associates, Inc.      Software and System Engineering

More information about the devel mailing list