octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #44998] [MXE] On Windows side, 64-bit OF modul


From: Philip Nienhuis
Subject: [Octave-bug-tracker] [bug #44998] [MXE] On Windows side, 64-bit OF modules can be miscompiled
Date: Tue, 05 May 2015 10:59:55 +0000
User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:36.0) Gecko/20100101 Firefox/36.0 SeaMonkey/2.33

Follow-up Comment #11, bug #44998 (project octave):

Cross-building on Mageia-4 Linux.
I believe it is isl that fails (as I see log/isl showing the error)
Otherwise clean repo, updated with hg update -C

[OT]
BTW I still have the libmng build error on my fast PC I reported a while ago,
at libmng I always have to restart the build by retrying a few times with
...JOBS=1 until it continues with dbus (at which point I Ctrl-C and can
continue with ...JOBS=9). From a previous log (one of those ... JOBS=1
tries):

:
make[2]: Entering directory
'/home/philip/devel/octdev/mxe/mxe32_20140501/tmp-libmng/libmng-2.0.2'
/bin/sh ./libtool --tag=CC   --mode=compile x86_64-w64-mingw32-gcc
-DHAVE_CONFIG_H -I.  
-I/home/philip/devel/octdev/mxe/mxe32_20140501/usr/x86_64-w64-mingw32/include 
-g -O2 -c -o libmng_callback_xs.lo libmng_callback_xs.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_callback_xs.lo' failed
make[2]: *** [libmng_callback_xs.lo] Error 63
make[2]: Leaving directory
'/home/philip/devel/octdev/mxe/mxe32_20140501/tmp-libmng/libmng-2.0.2'
/home/philip/devel/octdev/mxe/mxe32_20140501/Makefile:728: recipe for target
'build-only-libmng' failed
make[1]: *** [build-only-libmng] Error 2
make[1]: Leaving directory '/home/philip/devel/octdev/mxe/mxe32_20140501'


I think that actual error could be misleading, I rather think of some race
condition. I usually build on a core i5 desktop with a fairly fast SSD. On my
alternative build box (a core i5 laptop with "legacy" HDD) this build failure
never happened.


    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?44998>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]