public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug dynamic-link/30125] New: [regression, bisected] glibc-2.37 creates new symlink created in for libraries without soname
@ 2023-02-15  0:22 joanbrugueram at gmail dot com
  2023-02-15  0:22 ` [Bug dynamic-link/30125] [regression, bisected] glibc-2.37 creates new symlink created " joanbrugueram at gmail dot com
                   ` (7 more replies)
  0 siblings, 8 replies; 9+ messages in thread
From: joanbrugueram at gmail dot com @ 2023-02-15  0:22 UTC (permalink / raw)
  To: glibc-bugs

https://sourceware.org/bugzilla/show_bug.cgi?id=30125

            Bug ID: 30125
           Summary: [regression, bisected] glibc-2.37 creates new symlink
                    created in for libraries without soname
           Product: glibc
           Version: 2.37
            Status: UNCONFIRMED
          Severity: minor
          Priority: P2
         Component: dynamic-link
          Assignee: unassigned at sourceware dot org
          Reporter: joanbrugueram at gmail dot com
  Target Milestone: ---

Since installing glibc-2.37 I have noticed that `ldconfig` creates symlinks it
did not previously create for libraries without a soname.

In particular, if a library is for exmple named `libsomething.so.123.456.789`,
running `ldconfig` will now create a symlink named `libsomething.123` pointing
to `libsomething.123.456.789`, whereas previously it did not create this
symlink.

A complete reproducer is:

    #!/usr/bin/env sh
    set -eu

    rm -rf sonametest
    mkdir -p sonametest/etc sonametest/usr/lib
    gcc /dev/null -o sonametest/usr/lib/libtestsoname.so.123.456.789 -shared

    ldconfig -r sonametest
    ls -l1 sonametest/usr/lib/

Output with glibc-2.36:

    -rwxr-xr-x 1 user user 14520 11. Feb 12:34 libtestsoname.so.123.456.789

Output with glibc-2.37:

    lrwxrwxrwx 1 user user    28 11. Feb 12:34 libtestsoname.so.123 ->
libtestsoname.so.123.456.789
    -rwxr-xr-x 1 user user 14520 11. Feb 12:34 libtestsoname.so.123.456.789

I have bisected the change in behavior to commit
8ee878592c4a642937152c8308b8faef86bcfc40 "Assume only FLAG_ELF_LIBC6 suport".
It appears that the refactor in `implicit_soname` picked the wrong branch of
the `if` so `implicit_soname` now behaves always behaves as it did for libc4
libraries.

The only negative effect I have noticed from this is that unnecessary files are
created on the system.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

^ permalink raw reply	[flat|nested] 9+ messages in thread
end of thread, other threads:[~2023-02-20 16:32 UTC | newest]

Thread overview: 9+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-02-15  0:22 [Bug dynamic-link/30125] New: [regression, bisected] glibc-2.37 creates new symlink created in for libraries without soname joanbrugueram at gmail dot com
2023-02-15  0:22 ` [Bug dynamic-link/30125] [regression, bisected] glibc-2.37 creates new symlink created " joanbrugueram at gmail dot com
2023-02-15  0:23 ` [Bug dynamic-link/30125] [regression, bisected] glibc-2.37 creates new symlink " joanbrugueram at gmail dot com
2023-02-15  0:23 ` joanbrugueram at gmail dot com
2023-02-15  0:34 ` joanbrugueram at gmail dot com
2023-02-15  9:21 ` sam at gentoo dot org
2023-02-20 12:35 ` cvs-commit at gcc dot gnu.org
2023-02-20 12:36 ` adhemerval.zanella at linaro dot org
2023-02-20 16:32 ` cvs-commit at gcc dot gnu.org

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).