From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Rongqing Li <rongqing.li@windriver.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] kmod: remove the setting of INHIBIT_PACKAGE_STRIP
Date: Wed, 17 Sep 2014 08:23:56 +0100 [thread overview]
Message-ID: <1410938636.14624.66.camel@ted> (raw)
In-Reply-To: <5418D4FF.9030103@windriver.com>
On Wed, 2014-09-17 at 08:25 +0800, Rongqing Li wrote:
>
> On 09/16/2014 05:46 PM, Burton, Ross wrote:
> > On 15 September 2014 09:27, <rongqing.li@windriver.com> wrote:
> >> Setting INHIBIT_PACKAGE_STRIP is added by 61cb45869c[kmod: ptest fixes], but I
> >> can not reproduce the described issue, and seems it make wrong logical [
> >> when enable ptest, INHIBIT_PACKAGE_STRIP is always 1; and when disable ptest,
> >> INHIBIT_PACKAGE_STRIP is always 0]
> >
> > I take my comment back:
> >
> > ERROR: runstrip: ''arm-poky-linux-gnueabi-strip' --strip-debug
> > --remove-section=.comment --remove-section=.note --preserve-dates
> > '/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-arm/build/build/tmp/work/armv5te-poky-linux-gnueabi/kmod/18+gitAUTOINC+ae58de0fcb-r0/package/usr/lib/kmod/ptest/testsuite/rootfs/test-dependencies/lib/modules/4.0.20-kmod/kernel/fs/mbcache.ko''
> > strip command failed
> >
> > The autobuilder failed dramatically on this.
> >
> > Instead of inhibiting the strip globally, I wonder if there's a way to
> > avoid stripping the test suite.
> >
> > Ross
> >
>
> OK, I will see it
If there isn't, we should perhaps add something...
Cheers,
Richard
next prev parent reply other threads:[~2014-09-17 7:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-15 8:27 [PATCH] kmod: remove the setting of INHIBIT_PACKAGE_STRIP rongqing.li
2014-09-15 14:32 ` Burton, Ross
2014-09-17 10:11 ` Tudor Florea
2014-09-17 23:11 ` Khem Raj
2014-09-16 9:46 ` Burton, Ross
2014-09-17 0:25 ` Rongqing Li
2014-09-17 7:23 ` Richard Purdie [this message]
2014-09-17 7:32 ` Rongqing Li
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=1410938636.14624.66.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=rongqing.li@windriver.com \
/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