On 6/11/05, David Neary <[EMAIL PROTECTED]> wrote:

> This could be because the directory where the older GIMP libraries are
> installed is in /etc/ld.so.conf - I seem to recall that this plays havoc
> with link-time linking (which libtool does) and definitely does with
> runtime linking. I'm not sure what the solution might be if you've
> installed an official 2.2 or 2.0 GIMP in /usr, and you want to install
> 2.3.1 in /usr/local or /some/special/prefix - perhaps someone else can
> give ideas how to get around that problem.

the 2.2 libraries can be in /etc/ld.so.conf's path, but the 2.3 cannot be.

$ ldd `which gimp`
        libgimpwidgets-2.0.so.0 => /usr/lib/libgimpwidgets-2.0.so.0 (0x40030000)
        libgimpmodule-2.0.so.0 => /usr/lib/libgimpmodule-2.0.so.0 (0x4010e000)

$ ldd `which gimp-2.3`
        libgimpwidgets-2.0.so.0 =>
/usr/unstable/lib/libgimpwidgets-2.0.so.0 (0x40018000)
        libgimpmodule-2.0.so.0 =>
/usr/unstable/lib/libgimpmodule-2.0.so.0 (0x40106000)

where /usr/lib is always in the ldconfig path, and /usr/unstable/lib
is most definitely not.

Gimp-developer mailing list

Reply via email to