From: Andreas Schwab <schwab@linux-m68k.org>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: binutils@sourceware.org
Subject: Re: puzzling ld behavior, failing to find symbols from .so after adding more .o file
Date: Sat, 26 Mar 2022 16:19:35 +0100 [thread overview]
Message-ID: <87zglcg2rc.fsf@igel.home> (raw)
In-Reply-To: <ed16cdc8-3c01-22ed-ac30-e91648c97edd@msgid.tls.msk.ru> (Michael Tokarev's message of "Fri, 25 Mar 2022 23:15:20 +0300")
On Mär 25 2022, Michael Tokarev wrote:
> Is there a way to tell ld to emit some debugging info about its symbol
> lookup/resolution happenings?
Try generating a linker map file with -Wl,-Map=mapfile.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
prev parent reply other threads:[~2022-03-26 15:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-25 20:15 Michael Tokarev
2022-03-25 22:43 ` Andrew Bell
2022-03-26 14:56 ` Michael Tokarev
2022-03-26 0:25 ` Andrew Pinski
2022-03-26 15:06 ` Michael Tokarev
2022-03-26 15:19 ` Michael Tokarev
2022-03-30 1:50 ` Alan Modra
2022-03-26 15:19 ` Andreas Schwab [this message]
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=87zglcg2rc.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=binutils@sourceware.org \
--cc=mjt@tls.msk.ru \
/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).