Re: [MXE MinGW] miscompiled gcc for --enable64?

[Philip Nienhuis]

JohnD wrote:
> -----Original Message-----
> From: Philip Nienhuis [mailto:address@hidden
>>
<snip>
> > BTW as of lately my cross-builds often get stuck while building libmng; it
> stops
> > with a complaint about mismatching autoconf versions (1.4 versus 1.4.2
> IIRC).
>
> I haven't had any issues with libmng on my system - looking in the log file,
> I see a
> Main::scan_file() called too early to check prototype.
> Out of interest what -j option is used for make for you?
>
> Libtool is v 2.4.2, the version with libmng is 2.4, however calls
> autoreconfig in the .mk file.
> Perhaps it needs the force option?

You're right, I got it mixed up here (had to boot into Linux to find the 
actual error), it is libtool not autoconf:

<while building libmng>
:
:
/bin/sh ./libtool --tag=CC   --mode=compile x86_64-w64-mingw32-gcc 
-DHAVE_CONFIG_H -I. 
-I/home/philip/devel/octdev/mxe/mxe64_20141208/usr/x86_64-w64-mingw32/include 
 -g -O2 -c -o libmng_filter.lo libmng_filter.c
libtool: Version mismatch error.  This is libtool 2.4.2, but the
libtool: definition of this LT_INIT comes from libtool 2.4.
libtool: You should recreate aclocal.m4 with macros from libtool 2.4.2
libtool: and run autoconf again.
Makefile:409: recipe for target 'libmng_display.lo' failed
make[2]: *** [libmng_display.lo] Error 63
make[2]: *** Waiting for unfinished jobs....
:

Sometimes just restarting the build makes it go through; other times it 
stubbornly keeps hanging at this stage. So it looks like some timing 
issue or race condition.

As to "force" - I wouldn't know; but perhaps the "JOBS=9" parameter on 
the "make zip-dist" call is in the way?
I tried with JOBS=1 as well (after a build got stuck at libmng) but that 
didn't make much difference.

Philip