Hi all,
On Tue, 13 Sep 2011 08:40:34 +0200
Stephan Bergmann <sbergman@redhat.com>
wrote:
On 09/13/2011 08:18 AM, Stephan Bergmann wrote:
On 09/12/2011 11:23 PM, Norbert Thiebaud wrote:
On Mon, Sep 12, 2011 at 4:04 PM, Peter
Foley<pefoley2@verizon.net> wrote:
Another gbuild conversion.
Nice.
Pushed, Thanks.
It ~looks like this broke the latest Mac OSX gcc-4.0.1 (PPC)
tinderbox build, see
<http://tinderbox.libreoffice.org/cgi-bin/gunzip.cgi?tree=MASTER&brief-log=1315881022.32373>.
(Though I have no clue what went wrong; at least cannot easily
reproduce on unxlngx6.pro.)
I think the problem is using static libraries. IIRC, on Mac OS X, if
you link against two static libs -lA -lB, order is important, and if
B need symbols from A (that the executable into which the two are
linked does not already take from A), it won't find them. What could
help in this specific case is to switch the order of x2c_support and
x2c_xcd in xml2cmp/Executable_*.mk. (Will try that out on my Mac,
but that can take a while. Another solution might be to use Mac OS X
ld switches -all_load or -force_load.)
at
http://cgit.freedesktop.org/libreoffice/core/tree/solenv/gbuild/platform/unxgcc.mk#n312
for the general gcc case we are wrapping the static libs in the linker
command in start-group/end-group, which should help, but it seems like
this is missing on the osx platform files. Maybe doing the same there
would help?
Best,
Bjoern
--
https://launchpad.net/~bjoern-michaelsen
Context
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.