This is the mail archive of the
mailing list for the binutils project.
Re: [PATCH 2/2 v5] gold: enable new dtags by default
- From: Ian Lance Taylor <iant at google dot com>
- To: "H.J. Lu" <hjl dot tools at gmail dot com>
- Cc: Mike Frysinger <vapier at gentoo dot org>, binutils at sourceware dot org
- Date: Mon, 4 Feb 2013 21:43:04 -0800
- Subject: Re: [PATCH 2/2 v5] gold: enable new dtags by default
- References: <email@example.com> <firstname.lastname@example.org> <email@example.com> <CAKOQZ8ykkw_qvScz-dYyHnTEqEuz-Ccp1Uhfr5e1F31JM1KiTA@mail.gmail.com> <CAMe9rOoRUxVop0cEaC9eM7RU17d+2cmR+h+6UEqTr+wxM8LNKg@mail.gmail.com>
On Mon, Feb 4, 2013 at 5:44 PM, H.J. Lu <firstname.lastname@example.org> wrote:
> This caused:
> I changed BFD linker not set new dtags with -rpath.
I don't see why that is the right fix. Since DT_RPATH/DT_RUNPATH are
only ever set by the linker's -rpath option, it seems like the right
fix is to always use DT_RPATH and never use DT_RUNPATH.
Of course, since the only thing --new-dtags does in gold is select
DT_RUNPATH rather than DT_RPATH, this makes new--dtags completely
useless in gold.
It seems that we have made sensible-seeming decisions to wind up in an
absurd place. It seems that we should now make --new-dtags a no-op
and drop all support for generating DT_RUNPATH. Which makes me wonder
why DT_RUNPATH was invented in the first place.