public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jsm28 at gcc dot gnu dot org" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug libc/3378] New: ldconfig handling of links not to soname Date: Wed, 18 Oct 2006 00:20:00 -0000 [thread overview] Message-ID: <20061018001954.3378.jsm28@gcc.gnu.org> (raw) This is related to but not the same as bug 1484. I actually think ldconfig is probably working as designed here and no change is needed, but I'm not sure. Suppose that you have a symlink libfoo.so.1 -> subdir/libbar.so.1.1 where subdir/libbar.so.1.1 is the real file and libbar.so.1 is the SONAME. This is a variant on the arrangements in http://sourceware.org/ml/libc-alpha/2003-08/msg00128.html but in this case libfoo.so.1 is an extra compatibility symlink because we suppose some programs expect that SONAME and libbar.so.1 provides the same interface. We reach the code /* If the path the link points to isn't its soname and it is not .so symlink for ld(1) only, we treat it as a normal file. */ and it treats libfoo.so.1 as if it were an ordinary file like libc-2.5.so. Thus a symlink libbar.so.1 -> libfoo.so.1 is created and entered in the cache. The "problem" is that libfoo.so.1 doesn't get entered in the cache under that name; only the name libbar.so.1. The same applies whatever name or link in the subdirectory libfoo.so.1 is linked to. This illustrates that there are use cases where the soname should be entered (the above referenced message) but also ones where the link itself should be entered under its own name. Is the case given here something that should actually work? If so, I have a patch that causes both the link and the soname to be entered in the cache. If not, perhaps it should be made clearer what cases ldconfig supports. -- Summary: ldconfig handling of links not to soname Product: glibc Version: 2.4 Status: NEW Severity: enhancement Priority: P3 Component: libc AssignedTo: drepper at redhat dot com ReportedBy: jsm28 at gcc dot gnu dot org CC: glibc-bugs at sources dot redhat dot com http://sourceware.org/bugzilla/show_bug.cgi?id=3378 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
next reply other threads:[~2006-10-18 0:20 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-10-18 0:20 jsm28 at gcc dot gnu dot org [this message] 2010-05-04 15:26 ` [Bug libc/3378] " jsm28 at gcc dot gnu dot org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20061018001954.3378.jsm28@gcc.gnu.org \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sources.redhat.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).