From: Alejandro Colomar <alx.manpages@gmail.com>
To: Joachim Wuttke <j.wuttke@fz-juelich.de>, binutils@sourceware.org
Cc: linux-man@vger.kernel.org
Subject: Re: man ld(1): see also ldd, ldconfig
Date: Thu, 17 Nov 2022 00:49:47 +0100 [thread overview]
Message-ID: <08710003-7f8a-7583-cc79-cb51fbb8d859@gmail.com> (raw)
In-Reply-To: <9ed5e1a7-7003-e31f-1a39-62d2c3e718cc@fz-juelich.de>
[-- Attachment #1.1: Type: text/plain, Size: 1340 bytes --]
Hi Joachim,
On 11/15/22 17:51, Joachim Wuttke wrote:
> I'd suggest to add ldd and ldconfig to the "see also" section of man ld,
> because those are the man pages you need when desperately debugging
> ld failures on misconfigured systems.
I'd also add ld.so(8).
The page ld(1) is not provided by the Linux man-pages, but by the GNU binutils
project.
I added them to this mail.
>
> Thanks for all your work on the Linux man pages project, Joachim
Thanks! :-)
Cheers,
Alex
>
>
> ------------------------------------------------------------------------------------------------
> ------------------------------------------------------------------------------------------------
> Forschungszentrum Juelich GmbH
> 52425 Juelich
> Sitz der Gesellschaft: Juelich
> Eingetragen im Handelsregister des Amtsgerichts Dueren Nr. HR B 3498
> Vorsitzender des Aufsichtsrats: MinDir Volker Rieke
> Geschaeftsfuehrung: Prof. Dr.-Ing. Wolfgang Marquardt (Vorsitzender),
> Karsten Beneke (stellv. Vorsitzender), Prof. Dr. Astrid Lambrecht,
> Prof. Dr. Frauke Melchior
> ------------------------------------------------------------------------------------------------
> ------------------------------------------------------------------------------------------------
--
<http://www.alejandro-colomar.es/>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
parent reply other threads:[~2022-11-16 23:49 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <9ed5e1a7-7003-e31f-1a39-62d2c3e718cc@fz-juelich.de>]
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=08710003-7f8a-7583-cc79-cb51fbb8d859@gmail.com \
--to=alx.manpages@gmail.com \
--cc=binutils@sourceware.org \
--cc=j.wuttke@fz-juelich.de \
--cc=linux-man@vger.kernel.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).