From: LiLy <xmlymt@hotmail.com>
To: <iant@google.com>
Cc: <gcc-help@gcc.gnu.org>
Subject: RE: Shared librares dependency at compile time
Date: Fri, 27 Jul 2012 20:23:00 -0000 [thread overview]
Message-ID: <BLU154-W129386D9155DDBEFDDB301D6C10@phx.gbl> (raw)
In-Reply-To: <CAKOQZ8z3dU+NMVXxTFAMzG0QrbgDFgV7SywAaNeK_OAtXWubcw@mail.gmail.com>
Hi Ian,
Thanks for sharing!
Just found a discussion on GNU ld and gold.
http://code.google.com/p/mclinker/wiki/RelatedWork
Best Regards,
Ly
----------------------------------------
> Date: Fri, 27 Jul 2012 13:10:58 -0700
> Subject: Re: Shared librares dependency at compile time
> From: iant@google.com
> To: xmlymt@hotmail.com
> CC: gcc-help@gcc.gnu.org
>
> On Fri, Jul 27, 2012 at 12:56 PM, LiLy <xmlymt@hotmail.com> wrote:
> >
> > Glad to get your confirmations. Further more, could you please give me some links that introduce ld internals?
>
> I'm fond of http://www.airs.com/blog/archives/38 and subsequent entries.
>
> > BTW, I guess gold means google ld. Regarding 1.1), I suppose gold will also work in similar way, since the obj/lib file formats are same.
>
> gold isn't google ld, it's just gold. it's a new linker that is part
> of the GNU binutils.
>
> There is a key difference between GNU ld and gold in this area. If
> you link against liba.so, and liba.so has a DT_NEEDED entry pointing
> to libb.so, then GNU ld will attempt to replicate the dynamic linker's
> search path and find libb.so. gold will not do that. Because of
> that, GNU ld by default will warn about undefined symbols in liba.so,
> while gold by default will not.
>
> It is quite rare for this difference to actually matter.
>
> Ian
next prev parent reply other threads:[~2012-07-27 20:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-27 19:10 LiLy
2012-07-27 19:19 ` Ian Lance Taylor
2012-07-27 19:56 ` LiLy
2012-07-27 20:11 ` Ian Lance Taylor
2012-07-27 20:23 ` LiLy [this message]
2012-07-27 20:30 ` LiLy
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=BLU154-W129386D9155DDBEFDDB301D6C10@phx.gbl \
--to=xmlymt@hotmail.com \
--cc=gcc-help@gcc.gnu.org \
--cc=iant@google.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).