public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fweimer at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug dynamic-link/28237] ldconfig: /lib64/ld-linux-x86-64.so.2 is not a symbolic link
Date: Thu, 19 Aug 2021 12:24:00 +0000 [thread overview]
Message-ID: <bug-28237-131-CVJS4h2S0Z@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28237-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=28237
Florian Weimer <fweimer at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |WORKSFORME
Status|WAITING |RESOLVED
--- Comment #6 from Florian Weimer <fweimer at redhat dot com> ---
That documention still mentioned LinuxThreads, so it's been out of date for
about 18 years. The “make install” command mentioned there doesn't work,
either.
You really should install glibc into a clean chroot/sysroot using “make install
DESTDIR=…”, or use a package manager. This is the only way to avoid cruft from
a previous installation.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2021-08-19 12:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-17 8:44 [Bug dynamic-link/28237] New: " dilyan.palauzov at aegee dot org
2021-08-17 18:26 ` [Bug dynamic-link/28237] " fweimer at redhat dot com
2021-08-17 18:30 ` dilyan.palauzov at aegee dot org
2021-08-17 18:38 ` fweimer at redhat dot com
2021-08-17 19:13 ` dilyan.palauzov at aegee dot org
2021-08-18 6:38 ` dilyan.palauzov at aegee dot org
2021-08-19 12:24 ` fweimer at redhat dot com [this message]
2021-08-19 12:30 ` dilyan.palauzov at aegee 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=bug-28237-131-CVJS4h2S0Z@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).