From: Michael Tokarev <mjt@tls.msk.ru>
To: Andrew Bell <andrew.bell.ia@gmail.com>
Cc: Binutils <binutils@sourceware.org>
Subject: Re: puzzling ld behavior, failing to find symbols from .so after adding more .o file
Date: Sat, 26 Mar 2022 17:56:24 +0300 [thread overview]
Message-ID: <75a1eb80-1f4d-5b7e-b9fd-18acfcc1daf0@msgid.tls.msk.ru> (raw)
In-Reply-To: <CACJ51z0Ka9qKK0JL4PTQzbXuNd+pYzaz_KarwTc4cfEE6jeKZA@mail.gmail.com>
26.03.2022 01:43, Andrew Bell wrote:
> On Fri, Mar 25, 2022 at 4:16 PM Michael Tokarev <mjt@tls.msk.ru <mailto:mjt@tls.msk.ru>> wrote:
>
> Hi!
>
> I've got a puzzling issue here which I need help with,
> at least some pointers as of where to dig.
>
> ...deleted...
>
> I'm quite lost here. The question is: why after ecountering dbwrap_ctdb.o,
> ld stops finding symbols in shared libraries which it were finding before,
> but still being able to find symbols in static libs? How to debug this,
> maybe to make a test case?
>
> There is certainly the LD_DEBUG environment variable.
Hm. LD_DEBUG seems to be something about ld.so (the runtime linker), not ld
(the build-time linker). If I set LD_DEBUG when invoking ld, it will print
how *ld* symbols are resolved, not how ld resolves symbols in the executable
being build. Or am I wrong?
Thank you!
/mjt
next prev parent reply other threads:[~2022-03-26 14:56 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 [this message]
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
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=75a1eb80-1f4d-5b7e-b9fd-18acfcc1daf0@msgid.tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=andrew.bell.ia@gmail.com \
--cc=binutils@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).