Re: cl.exe and system types

2018-08-24 Thread Sébastien Hinderer
Dear Earnie and Keith, Many thanks for your support, warmly appreciated. Earnie (2018/08/23 13:08 -0400): > It's going to depend on what you want. If you're using the crosstools > for MinGW-w64 then you would specify --host as {i686,x86_64}-w64-mingw32 > and --build as {i686,x86_64}-pc-cygwin.

Re: cl.exe and system types

2018-08-24 Thread Keith Marshall
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 24/08/18 09:23, Sébastien Hinderer wrote: > Keith Marshall (2018/08/23 20:00 +0100): >> For --build, the output from config.guess should always be >> suitable; for --host, it may be okay to affix an arbitrary >> suffix to mingw32, such as (untested

Re: cl.exe and system types

2018-08-24 Thread Sébastien Hinderer
Keith Marshall (2018/08/24 10:50 +0100): > > But why would you include a "mingw" string in something that does > > not use mingw at all? > > Because it's an OS name already known to config.sub, and because it's > an OS designator which is specific to native MS-Windows software > builds, (but see

Skip all version checks with autoconf?

2018-08-24 Thread Jeffrey Walton
I'm catching this error on Fedora 28, x86_64, fully patched: $ autoreconf -fi configure.ac:35: error: require Automake 1.16.1, but have 1.15.1 autoreconf: automake failed with exit status: 1 This is a chronic problem with Autotools. Nearly every program that gets patched has a problem like this.

Re: Skip all version checks with autoconf?

2018-08-24 Thread Eric Blake
On 08/24/2018 04:55 PM, Jeffrey Walton wrote: I'm catching this error on Fedora 28, x86_64, fully patched: $ autoreconf -fi configure.ac:35: error: require Automake 1.16.1, but have 1.15.1 autoreconf: automake failed with exit status: 1 You'll need to ask whatever project you are trying to bui

Re: Skip all version checks with autoconf?

2018-08-24 Thread Jeffrey Walton
> It is not autoconf's problem when someone writes a configure.ac that wrongly > claims to use too-new of a version of automake. But if you don't think the > package is actually relying on a feature that only that newer automake > provided, you are welcome to edit configure.ac and change the > AM_

Re: Skip all version checks with autoconf?

2018-08-24 Thread Jeffrey Walton
On Fri, Aug 24, 2018 at 6:59 PM, Jeffrey Walton wrote: >> It is not autoconf's problem when someone writes a configure.ac that wrongly >> claims to use too-new of a version of automake. But if you don't think the >> package is actually relying on a feature that only that newer automake >> provide