From: Ian Campbell <ian.campbell@citrix.com>
To: Wei Liu <wei.liu2@citrix.com>
Cc: xen-devel@lists.xenproject.org,
Daniel Kiper <daniel.kiper@oracle.com>,
ian.jackson@eu.citrix.com, stefano.stabellini@eu.citrix.com
Subject: Re: [PATCH v2] tools: link executables with libtinfo explicitly
Date: Wed, 3 Jun 2015 11:35:50 +0100 [thread overview]
Message-ID: <1433327750.7108.65.camel@citrix.com> (raw)
In-Reply-To: <20150602165824.GZ19403@zion.uk.xensource.com>
On Tue, 2015-06-02 at 17:58 +0100, Wei Liu wrote:
> On Tue, Jun 02, 2015 at 03:33:26PM +0200, Daniel Kiper wrote:
> > binutils 2.22 changed ld default from --copy-dt-needed-entries
> > to -no-copy-dt-needed-entries. This revealed that some objects
> > are linked implicitly with libtinfo and newer ld fails to build
> > relevant executables.
For future reference "relevant executables" would be better as a list of
the actual affected programs...
> >
> > Below is short explanation why we should not do that...
> >
> > http://fedoraproject.org/wiki/UnderstandingDSOLinkChange says:
> >
> > The default behaviour for ld (my note: before version 2.22) allows
> > users to 'indirectly' link to required objects/libraries through
> > intermediate objects/libraries. While this is convenient, it can
> > also be dangerous because it makes your program's dependencies tied
> > to the dependencies of other objects. If those objects ever change
> > their linkages, they can break your program without any changes
> > to your own code!
> >
> > Please run autoconf in tools directory.
> >
> > Signed-off-by: Daniel Kiper <daniel.kiper@oracle.com>
>
> Acked-by: Wei Liu <wei.liu2@citrix.com>
Applied, running autoconf.
Ian.
next prev parent reply other threads:[~2015-06-03 10:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-02 13:33 [PATCH v2] tools: link executables with libtinfo explicitly Daniel Kiper
2015-06-02 16:58 ` Wei Liu
2015-06-03 10:35 ` Ian Campbell [this message]
2015-06-03 11:08 ` Daniel Kiper
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=1433327750.7108.65.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=daniel.kiper@oracle.com \
--cc=ian.jackson@eu.citrix.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xenproject.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 NNTP newsgroup(s).