Matthias Klose <[EMAIL PROTECTED]> writes:
> Goswin Brederlow writes:
>> libffi.la has the following libdir:
>>
>> libdir='/usr/lib/../lib'
>>
>> That cuases libtool to add the rpath option when linking against the
>> library which in turn prevents shlibs to work (since no package
>> contains /usr/lib/../lib/libffi.so) which in turn miscompiles
>> e.g. sablevm which in turn causes FTBFS for a lot of java packages.
>>
>> MfG
>> Goswin
>>
>>
>> -- System Information:
>> Debian Release: testing/unstable
>> APT prefers unstable
>> APT policy: (500, 'unstable')
>> Architecture: i386 (x86_64)
>> Kernel: Linux 2.6.5-amd64
>
> is this only the case for the amd64 architecture? Then it should not
> be severity grave.
>
> Matthias
No, this was the i386 case. On amd64 it is /usr/lib/../lib64 resulting
in much the same problems.
Unless libffi.la, libtool or dpkg-shlibdep is changed for sarge the
libffi from gcc-3.4 will be broken for building debs.
MfG
Goswin
