From: Sergei Trofimovich <slyfox@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Checking if a package respects LDFLAGS
Date: Thu, 12 Oct 2017 11:56:57 +0100 [thread overview]
Message-ID: <20171012115657.5d76b6ab@sf> (raw)
In-Reply-To: <1506841339.842.0.camel@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1077 bytes --]
On Sun, 01 Oct 2017 09:02:19 +0200
Michał Górny <mgorny@gentoo.org> wrote:
> W dniu sob, 30.09.2017 o godzinie 21∶49 +0000, użytkownik Robin H.
> Johnson napisał:
> > On Sat, Sep 30, 2017 at 08:05:50PM +0200, Andreas K. Huettel wrote:
> > > Am Samstag, 30. September 2017, 19:03:59 CEST schrieb Keri Harris:
> > > > Hi,
> > > >
> > > > Is there a recommended method for testing if a package respects LDFLAGS?
> > > >
> > > > Arch testers are encouraged to add -Wl,--hash-style=gnu to LDFLAGS
> > > > [1],[2] and portage uses scanelf to check for .hash sections. However it
> > > > appears that ld defaults to using a .gnu.hash section:
> > >
> > > That test used to work, but it's broken now. We need a new one.
> >
> > How about something similar to Fedora's binary annotations work, or
> > injecting a .note.gentoo section into binaries (containing literal
> > C/CXX/LDFLAGS would be useful).
> >
>
> Portage team is always happy to accept any patch for this.
Tracking bug: https://bugs.gentoo.org/455232
--
Sergei
[-- Attachment #2: Цифровая подпись OpenPGP --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
prev parent reply other threads:[~2017-10-12 10:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-30 17:03 [gentoo-dev] Checking if a package respects LDFLAGS Keri Harris
2017-09-30 18:05 ` Andreas K. Huettel
2017-09-30 21:49 ` Robin H. Johnson
2017-10-01 7:02 ` Michał Górny
2017-10-12 10:56 ` Sergei Trofimovich [this message]
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=20171012115657.5d76b6ab@sf \
--to=slyfox@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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