On 13/12/10 18:07 , Martin Costabel wrote:
> On 13/12/10 16:39, Daniel Macks wrote:
>>
>> I've sen a few places where 10.4's linker is a bit more anal about
>> having dependent libs available at link-time. But it's always been
>> because a lib "somewhere in the dyld runtime loading tree" was missin
On 13/12/10 16:39, Daniel Macks wrote:
>
> I've sen a few places where 10.4's linker is a bit more anal about
> having dependent libs available at link-time. But it's always been
> because a lib "somewhere in the dyld runtime loading tree" was missing a
> direct link against a lib it used directly.
I've sen a few places where 10.4's linker is a bit more anal about
having dependent libs available at link-time. But it's always been
because a lib "somewhere in the dyld runtime loading tree" was missing
a direct link against a lib it used directly. On later 10.x, the
default is to look it up
On 13/12/10 14:33, Alexander Hansen wrote:
[]
> The really strange part is that /sw/lib/qt4-mac/lib/libQtCLucene.4.dylib
> is part of qt4-mac-* itself. I'll see if I can reproduce this on
> 10.4/powerpc.
It only looks strange. The dylib is built with an install_name of
/sw/lib/qt4-mac/lib/libQtC
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/13/10 6:01 AM, Martin Costabel wrote:
> From a Fink newbie who installed Fink solely in order to get scribus, I
> received the following error message. When I build this, it succeeds,
> and I have different linker flags. In particular, I do ha
From a Fink newbie who installed Fink solely in order to get scribus, I
received the following error message. When I build this, it succeeds,
and I have different linker flags. In particular, I do have
-lQtCLucene
on the linker line. More precisely, I have the following additional flags
-
