From: Tom Rini <tom_rini@mentor.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: RFC: Should do_runstrip be removed for kernel packages?
Date: Fri, 25 Jun 2010 08:50:59 -0500 [thread overview]
Message-ID: <4C24B443.80303@mentor.com> (raw)
In-Reply-To: <4C227543.3050502@zenlinux.com>
Scott Garman wrote:
> Hello,
>
> I've noticed for many kernel builds in OE/Poky that there are non-fatal
> runstrip errors being generated during the do_pacakge stage of the build.
>
> This is happening because a handful of utility binaries (in arch/boot/
> and scripts/) are being compiled for the host architecture, and then
> strip for the target architecture is being run. When these architectures
> don't match, runstrip complains and generates these errors.
>
> Currently in Poky we are maintaining a blacklist of these binaries and
> deleting them in do_install:
>
> http://git.pokylinux.org/cgit.cgi/poky/commit/?id=698dab01098816e4894beb4b3dad556f045c074d
>
>
> This is a hack that I'd like to keep as temporary as possible.
>
> I'm curious though if it is even common to perform do_runstrip for
> kernel packages? What are the use cases that require this? If there are
> none, then I'm inclined to simply disable do_runstrip in kernel.bbclass.
>
> Another option - less elegant, but better than the current hack - might
> be to use a variable to disable runstrip and set that within the kernel
> recipe files.
There's already a SKIP for strip, iirc. Throwing that into
kernel.bbclass or the modules bbclass would get the discussion moving
more, perhaps (I'm a bit torn here).
--
Tom Rini
Mentor Graphics Corporation
prev parent reply other threads:[~2010-06-25 13:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-23 20:57 RFC: Should do_runstrip be removed for kernel packages? Scott Garman
2010-06-25 13:50 ` Tom Rini [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=4C24B443.80303@mentor.com \
--to=tom_rini@mentor.com \
--cc=openembedded-devel@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