From: Florian Weimer <fweimer@redhat.com>
To: Lv Ying via Libc-help <libc-help@sourceware.org>
Cc: Lv Ying <lvying.system.thoughts@gmail.com>
Subject: Re: ldconfig is statically linked or dynamiclly linked
Date: Thu, 01 Sep 2022 14:19:07 +0200 [thread overview]
Message-ID: <87ilm7qock.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <3f822786-189c-1c45-9415-be3f1abe916b@gmail.com> (Lv Ying via Libc-help's message of "Thu, 1 Sep 2022 17:41:39 +0800")
* Lv Ying via Libc-help:
> So ldconfig is dynamiclly linked or statically linked?
Usually, glibc ldconfig is statically linked. The output of the file
tool is notoriously unreliable.
> I think ldconfig may be statically linked, and can ldconfig be only
> statically linked?
It's technically possible to link it dynamically, with a few makefile
changes, but we don't do that, to make it easier to recover from certain
failure scenarios.
Thanks,
Florian
next prev parent reply other threads:[~2022-09-01 12:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-01 9:41 Lv Ying
2022-09-01 12:19 ` Florian Weimer [this message]
2022-09-01 12:22 ` Siddhesh Poyarekar
2022-09-01 13:15 ` Adhemerval Zanella Netto
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=87ilm7qock.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.com \
--cc=libc-help@sourceware.org \
--cc=lvying.system.thoughts@gmail.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: 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).