[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#632682: kfreebsd-amd64 and /lib64 -> lib symlink



On Fri, Aug 19, 2011 at 10:12:31AM +0200, Sven Joachim wrote:
> > I looked at just commited r4891, and it seems that it breaks
> > kfreebsd-amd64 seriously.

> > On kfreebsd-amd64, the ELF interpreter is
> > "/lib/ld-kfreebsd-x86-64.so.1", i.e. it is really in /lib, not in
> > /lib64.

> > The "lib64 -> lib" symlinks in previous eglibc versions only have been
> > as defence against broken packages shipping their libs in lib64.

> > This part of libc.preinst seems to delete our ELF interpreter:
> > remove_lib64_symlink() {
> > ...
> > rm -f /lib/$(basename RTLD_SO)
> > }

> > On kfreebsd-amd64 the "lib64 -> lib" symlinks are optional,
> > but "/lib/ld-kfreebsd-x86-64.so.1" is not ;-)

> Right.  I deliberately omitted kfreebsd-amd64 from the list of
> architectures where this code is run, but vorlon silently added it.

Ah, I had assumed this was an oversight in your patch since it was part of
the bug thread but not included in your patch... i.e., you had silently
dropped it ;)

So we don't want to remove the symlink from /lib or add it to /lib64 on
kfreebsd-amd64, but we do still want to get rid of the symlink itself.  But
since libc won't ship any files in /lib64 on kfreebsd-amd64, we don't need
to do any special symlink handling, dpkg will drop it for us on upgrade.

Fix committed - thanks for catching.

-- 
Steve Langasek                   Give me a lever long enough and a Free OS
Debian Developer                   to set it on, and I can move the world.
Ubuntu Developer                                    http://www.debian.org/
slangasek@ubuntu.com                                     vorlon@debian.org

Attachment: signature.asc
Description: Digital signature


Reply to: