public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "joanbrugueram at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug dynamic-link/30125] [regression, bisected] glibc-2.37 creates new symlink for libraries without soname
Date: Wed, 15 Feb 2023 00:34:55 +0000 [thread overview]
Message-ID: <bug-30125-131-X6veiSiI2T@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30125-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=30125
--- Comment #1 from Joan Bruguera Micó <joanbrugueram at gmail dot com> ---
For completeness, details about the system where this reproduces:
Host/build/target are the same
Target triplet: x86_64-pc-linux-gnu
Configure command: ./configure --prefix=/usr
OS: Arch Linux, updated as of 2023-02-14; also reproduces current Fedora 37/38
containers from DockerHub
Linux version: 6.1.11 (-arch1-1 variant)
gcc version: gcc-Version 12.2.1 20230201 (GCC)
ld version: GNU ld (GNU Binutils) 2.40
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-02-15 0:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-15 0:22 [Bug dynamic-link/30125] New: [regression, bisected] glibc-2.37 creates new symlink created in " 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 [this message]
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
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=bug-30125-131-X6veiSiI2T@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@sourceware.org \
/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: link
Be 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).