octave-maintainers
[Top][All Lists]
Advanced

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

Re: mxe-octave native ming build


From: Michael Goffioul
Subject: Re: mxe-octave native ming build
Date: Wed, 26 Jun 2013 22:02:50 -0400

On Wed, Jun 26, 2013 at 9:55 PM, John D <address@hidden> wrote:

Somewhere between change set  http://hg.octave.org/mxe-octave/rev/076acecb9c21   and changeset http://hg.octave.org/mxe-octave/rev/21586f2d1fe7, Qt in the native build started failing in its build.

 

Qt log:

make[8]: Entering directory `/home/jdonoghue/mxe-octave/tmp-qt/qt-everywhere-ope

nsource-src-4.8.3/src/plugins/imageformats/mng'

C:/MinGW/msys/1.0/home/jdonoghue/mxe-octave/tmp-qt/qt-everywhere-opensource-src-

4.8.3/bin/qmake C:/MinGW/msys/1.0/home/jdonoghue/mxe-octave/tmp-qt/qt-everywhere

-opensource-src-4.8.3/src/plugins/imageformats/mng/mng.pro  -o Makefile -spec win32-g++

Project ERROR: Package libmng not found

make[8]: *** [all] Error 2

 

Libmng built ok (according to its log). Qt and libmng haven’t changed in these change sets, so I am guessing something changed with zlib or bzip2 that has then effected the build.

 

I will see if I can find the exact change set that broke it.


Do you have an error log about why libmng is not compiled? (assuming it is actually not compiled, but the error above seems to go in that direction). In those 2 changesets, the only change that could be suspicious is the addition of CC='$(MXE_CC)' to zlib.mk, though I don't see at the moment how it could affect a native MinGW build.

Michael.


reply via email to

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