On Fri, 2010-10-29 at 09:37 +0100, Michael Meeks wrote:
The KDE / stlport nasty is really awful though; I -thought- we agreed
to default to --without-stlport : Caolan - is that so ?
No, the problem is probably simple. And its not the cast that KDE is
linking against libstlport.
a) There is a /usr/lib/libstlport_gcc.so in some peoples distributions.
b) We have .../solver/lib/libstlport_gcc.so which we want to link
against, but we're linking against the other libstlport
c) When --enable-kde(something) is enabled there is some linker flag
being inserted into the start of the gcc command line to be "-L/usr/lib"
The obvious bustage is then because we're linking the kde plugin against
a different stlport than we linked everything else against. But the same
mismatch would exist if we happened to also link it against libxslt,
libxml2 etc. So disabling stlport for this specific reason is probably
the wrong thing to do.
So, the question is, where's /usr/lib coming from in the ENABLE_KDE
case, and can it be stuffed to the *end* of the compiler line and not
the start. I don't build against KDE, but I guess I could make an
exception for once and go see this for myself.
C.
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.