Re: libtiff borken - cannot build anymore?
Jay Berkenbilt <qjb@debian.org> writes:
> Ondřej Surý <ondrej@sury.org> wrote:
>> This results in:
>>
>> E: libgd-tools: binary-or-shlib-defines-rpath usr/bin/annotate
>> /usr/lib/x86_64-linux-gnu/libtiff5-alt
> Yes, I'm afraid that's unavoidable. This issue is mentioned in the
> README.Debian file. This works by installing the .so file in a
> non-standard location so that it can coexist with libtiff4, and linking
> in that way with libtool the rpath to be embedded. Once the tiff
> transition is completed and the packages are rebuilt, this problem will
> go away.
This shouldn't be required, since the two libtiff shared libraries can
both go into /usr/lib (since they have different SONAMEs). The only thing
that can't go into /usr/lib and has to go somewhere else is the *.so
symlink, which doesn't require an rpath setting, only a -L flag during
linking.
See the krb5-multidev and heimdal-multidev packages for how this is done.
--
Russ Allbery (rra@debian.org) <http://www.eyrie.org/~eagle/>
Reply to: