public inbox for
 help / color / mirror / Atom feed
From: Roland McGrath <>
To: "Joseph S. Myers" <>
Cc: <>,    <>
Subject: Re: Link extra-libs consistently with libc and
Date: Fri, 17 May 2013 21:42:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: Joseph S. Myers's message of  Friday, 17 May 2013 21:36:00 +0000 <>

> > elfobjdir and elf-objpfx are redundant.  We should consolidate on just one
> > or the other.  I don't think it matters which.  For linking, using
> > makes sense.  There is no need to use $(rtld-installed-name).
> I've added this consolidation to the wiki todo list.

Good enough.

> Now, maybe could be built in a different way that happens 
> after linkobj/ is built.  But the principle of consistency with 
> building with an installed compiler and libc suggests that linkobj/ 
> should only be used when necessary.

Fair enough.

> I'd think such a linker script might as well include absolute paths; a 

We take some pains in other places to avoid those.  It means you can move
your build directory around without breaking everything.

> No, tested with normal testsuite runs.  I don't expect everything to be 
> unchanged, given that various objects were previously linked 
> unconditionally with and after the patch have a --as-needed link 
> with (so some may not end up with a dependency on after all).

I'd like to see at least verification that no actual code changed, and
diffs of readelf -d output where it changed.


  reply	other threads:[~2013-05-17 21:42 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-09  0:22 Joseph S. Myers
2013-05-10  0:01 ` David Holsgrove
2013-05-14  0:32 ` Joseph S. Myers
2013-05-14  1:12   ` Roland McGrath
2013-05-17 20:24   ` Roland McGrath
2013-05-17 21:36     ` Joseph S. Myers
2013-05-17 21:42       ` Roland McGrath [this message]
2013-05-17 22:56         ` Joseph S. Myers
2013-05-17 23:12           ` Roland McGrath
2013-05-17 23:19     ` Joseph S. Myers
2013-05-28 23:58       ` Roland McGrath

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \

* 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).