|
| From: | Michael Goffioul |
| Subject: | Re: mxe-octave native ming build failure |
| Date: | Fri, 28 Jun 2013 19:02:34 -0400 |
From: Michael Goffioul [mailto:address@hidden]
Sent: Friday, June 28, 2013 3:20 PMSubject: Re: mxe-octave native ming build failure
To: John D
Cc: Octave Maintainers List; John W. Eaton; Philip Nienhuis
On Fri, Jun 28, 2013 at 3:06 PM, John D <address@hidden> wrote:
From: Michael Goffioul [mailto:address@hidden]
Sent: Wednesday, June 26, 2013 10:03 PM
To: John D
Cc: Octave Maintainers List; John W. Eaton; Philip Nienhuis
Subject: Re: mxe-octave native ming build
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.
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.
So it is changeset http://hg.octave.org/mxe-octave/rev/d89eccc2edd3 that causes it to fail.
There are 2 changes to zlib in that change set, the first being the removal of CC=MXE_CC. the second being that it doesn’t install the static libraries unless selected to do so.
I tried removing the CC part, so am guessing libmng is using the static zlib for some reason.
I was looking at your previous mail, and it appears libmng also installs the static library (though it shouldn't if --enable-static is not specified). So maybe what's happening is that Qt is using the static libmng, but fails to do so because it requires the static zlib. If I'm right, then the "solution" would be not to install the static version of libmng.
Michael.
Can it be set to use the ENABLE_SHARED_OR_STATIC?
| [Prev in Thread] | Current Thread | [Next in Thread] |