From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Mark Hatle <mark.hatle@windriver.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] insane: detect and warn about relocations in .text
Date: Wed, 07 Nov 2012 15:37:20 +0100 [thread overview]
Message-ID: <1352299040.8467.52.camel@ted> (raw)
In-Reply-To: <509A30ED.2070905@windriver.com>
On Wed, 2012-11-07 at 10:59 +0100, Mark Hatle wrote:
> On 11/6/12 6:24 PM, Phil Blundell wrote:
> > Ping?
>
> I do think we need this. Having the textrel does prevent prelinking as well.
Coming up to release I didn't really want to add more warnings and its
slipped through the cracks. I'll likely take this next week when things
quieten down a bit, ELC-E, the OE-GA, Yocto Project Dev day and so on
are making this one a little hectic.
Does anyone know how many warnings this is going to generate on an
OE-Core world build?
The biggest issue I have with these new tests is people also stepping up
and fixing the warnings they generate since often its a non-trivial
effort. The Yocto Project has been doing a lot here, quietly fixing a
lot of them up but more help would be much appreciated.
Cheers,
Richard
next prev parent reply other threads:[~2012-11-07 14:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-06 17:24 [PATCH] insane: detect and warn about relocations in .text Phil Blundell
2012-11-07 9:59 ` Mark Hatle
2012-11-07 14:37 ` Richard Purdie [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-10-03 15:42 Phil Blundell
2012-10-03 15:56 ` Mark Hatle
2012-10-03 10:24 Phil Blundell
2012-10-03 10:31 ` Martin Jansa
2012-10-03 10:44 ` Phil Blundell
2012-10-03 11:19 ` Richard Purdie
2012-10-03 12:39 ` Phil Blundell
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=1352299040.8467.52.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=mark.hatle@windriver.com \
--cc=openembedded-core@lists.openembedded.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