From: Chong Lu <Chong.Lu@windriver.com>
To: Tudor Florea <Tudor.Florea@enea.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] kmod: fix debuginfo is missing in shared library
Date: Fri, 24 Oct 2014 14:30:26 +0800 [thread overview]
Message-ID: <5449F202.8030206@windriver.com> (raw)
In-Reply-To: <26724FB0BFCB3D4C91BDE184751AA3A428ACB19F@SESTOEX04.enea.se>
On 10/24/2014 01:02 AM, Tudor Florea wrote:
>
> Hi,
>
> *From:*openembedded-core-bounces@lists.openembedded.org
> [mailto:openembedded-core-bounces@lists.openembedded.org] *On Behalf
> Of *Burton, Ross
> *Sent:* Thursday, October 23, 2014 17:21
> *To:* Chong Lu
> *Cc:* OE-core
> *Subject:* Re: [OE-core] [PATCH 1/1] kmod: fix debuginfo is missing in
> shared library
>
> On 21 October 2014 09:16, Chong Lu <Chong.Lu@windriver.com
> <mailto:Chong.Lu@windriver.com>> wrote:
>
> -INHIBIT_PACKAGE_STRIP = "${@bb.utils.contains(
> <mailto:$%7b@bb.utils.contains%28>"DISTRO_FEATURES", "ptest", "1",
> "0", d)}"
> +INHIBIT_PACKAGE_STRIP_${PN}-ptest = "${@bb.utils.contains(
> <mailto:$%7b@bb.utils.contains%28>"DISTRO_FEATURES", "ptest", "1",
> "0", d)}"
>
>
> Was this actually tested?
>
> 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-depmod/detect-loop/lib/modules/4.4.4/kernel/moduleA.ko''
> strip command failed
>
> INHIBIT_PACKAGE_STRIP isn't a per-package variable as stripping
> happens before the package-splitting. Moving it to happen after
> splitting won't be trivial as you'd need to know what package to put
> the resultant files into. Maybe we need a strip blacklist?
>
> Ross
>
> *//*
>
> */One way to solve this is to pack the ptest “sample” files during
> install (in do_install_append) and unpack back when running ptest on
> target (in run-ptest). The downside of this is we add a dependency on
> tar./*
>
> */Please let me know if it is acceptable and I’ll come with a patch
> for this./*
>
> */Regards,/*
>
> */Tudor./*
>
Thanks for your suggestion, I have sent a v2.
Best Regards
Chong
next prev parent reply other threads:[~2014-10-24 6:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-21 8:16 [PATCH 0/1] kmod: fix debuginfo is missing in shared library Chong Lu
2014-10-21 8:16 ` [PATCH 1/1] " Chong Lu
2014-10-23 14:21 ` Burton, Ross
2014-10-23 17:02 ` Tudor Florea
2014-10-24 6:30 ` Chong Lu [this message]
2014-10-24 6:28 ` Chong Lu
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=5449F202.8030206@windriver.com \
--to=chong.lu@windriver.com \
--cc=Tudor.Florea@enea.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