From: Lv Ying <lvying.system.thoughts@gmail.com>
To: libc-help@sourceware.org
Subject: ldconfig is statically linked or dynamiclly linked
Date: Thu, 1 Sep 2022 17:41:39 +0800 [thread overview]
Message-ID: <3f822786-189c-1c45-9415-be3f1abe916b@gmail.com> (raw)
Hi all:
I am confused when exec file ldconfig and ldd ldconfig on CentOS 8(glibc-2.28):
# which ldconfig
/usr/sbin/ldconfig
# file /usr/sbin/ldconfig
/usr/sbin/ldconfig: ELF 64-bit LSB shared object, x86-64, version 1 (GNU/Linux), dynamically linked, for GNU/Linux 3.2.0, BuildID[sha1]=90ddd9a3e194fb2ec4edd5184d9fca4df45af636, not stripped
# ldd /usr/sbin/ldconfig
statically linked
So ldconfig is dynamiclly linked or statically linked?
I lookup elf/Makefile:
ifeq (yes,$(use-ldconfig))
ifeq (yes,$(build-shared))
others-static += ldconfig
others += ldconfig
install-rootsbin += ldconfig
I think ldconfig may be statically linked, and can ldconfig be only statically linked?
next reply other threads:[~2022-09-01 9:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-01 9:41 Lv Ying [this message]
2022-09-01 12:19 ` Florian Weimer
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=3f822786-189c-1c45-9415-be3f1abe916b@gmail.com \
--to=lvying.system.thoughts@gmail.com \
--cc=libc-help@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).