From: Hongxu Jia <hongxu.jia@windriver.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
<ross.burton@intel.com>, <mark.hatle@windriver.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 03/17] conf/bitbake.conf package.bbclass: improve dbg package sources generation from work-shared
Date: Wed, 30 Mar 2016 13:36:14 +0800 [thread overview]
Message-ID: <56FB65CE.1050908@windriver.com> (raw)
In-Reply-To: <56FB32D3.3080504@windriver.com>
On 03/30/2016 09:58 AM, Hongxu Jia wrote:
>
>>
>> Its possible software may mix from shared-work and from some local
>> kernel module build too, not sure if/how well the code copes with that
>> case.
>
> Currently kernel module has no dbg package generated, but I will
> try to open it, and please wait my report for this case.
Hi Richard,
It is hardly to generate dbg for kernel module, it explicitly ignore
them and strip them.
In meta/classes/package.bbclass:
...
377 # We ignore kernel modules, we don't generate debug info files.
378 if file.find("/lib/modules/") != -1 and file.endswith(".ko"):
379 return 1
...
943 if (d.getVar('INHIBIT_PACKAGE_STRIP', True) != '1'):
944 for root, dirs, files in cpath.walk(dvar):
945 for f in files:
946 file = os.path.join(root, f)
947 if file.endswith(".ko") and
file.find("/lib/modules/") != -1:
948 kernmods.append(file)
949 continue
...
(I tried, but lots of failures and make no sense)
I could not get a case that software gets sources from shared-work and
local kernel module build. But if local kernel module build does not in
work-shared or software's WORKDIR, this fix could not do the collection
from local kernel module.
This fix could collect sources from work-shared and recipes's WORKDIR
(such as gcc).
//Hongxu
next prev parent reply other threads:[~2016-03-30 5:36 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-28 8:18 [PATCH V7 00/17] fix buildpaths QA issue && dbp package source generation Hongxu Jia
2016-03-28 8:18 ` [PATCH 01/17] conf/bitbake.conf package.bbclass: fix dbg package not contain sources while -fdebug-prefix-map used Hongxu Jia
2016-04-18 8:09 ` Andreas Müller
2016-04-18 8:11 ` Hongxu Jia
2016-04-18 8:23 ` Andreas Müller
2016-04-18 8:32 ` Hongxu Jia
2016-04-18 8:47 ` Andreas Müller
2016-04-18 9:04 ` Hongxu Jia
2016-04-18 9:15 ` Andreas Müller
2016-04-18 9:34 ` Hongxu Jia
2016-04-18 9:52 ` Andreas Müller
2016-04-18 13:08 ` Hongxu Jia
2016-04-18 13:55 ` Burton, Ross
2016-04-18 14:16 ` Andreas Müller
2016-04-18 14:51 ` Richard Purdie
2016-04-18 18:50 ` Mark Hatle
2016-04-18 21:05 ` Andreas Müller
2016-04-19 0:51 ` Mark Hatle
2016-04-19 4:32 ` Paul Eggleton
2016-04-19 12:29 ` Mark Hatle
2016-04-19 7:33 ` Hongxu Jia
2016-04-19 12:31 ` Mark Hatle
2016-04-19 12:59 ` Hongxu Jia
2016-04-19 14:11 ` Andreas Müller
2016-04-19 14:47 ` Mark Hatle
2016-04-19 14:49 ` Mark Hatle
2016-04-19 14:54 ` Richard Purdie
2016-04-19 21:50 ` Andreas Müller
2016-04-28 21:41 ` Andreas Müller
2016-04-19 1:46 ` Hongxu Jia
2016-03-28 8:18 ` [PATCH 02/17] gcc-5.3/gcc-4.9: -fdebug-prefix-map support to remap relative path Hongxu Jia
2016-03-28 8:18 ` [PATCH 03/17] conf/bitbake.conf package.bbclass: improve dbg package sources generation from work-shared Hongxu Jia
2016-03-29 22:38 ` Richard Purdie
2016-03-30 1:58 ` Hongxu Jia
2016-03-30 5:36 ` Hongxu Jia [this message]
2016-03-28 8:18 ` [PATCH 04/17] dtc.inc: fix buildpaths QA issue Hongxu Jia
2016-03-28 8:18 ` [PATCH 05/17] fix_buildpaths.bbclass: add bbclass to fix build path Hongxu Jia
2016-03-28 8:18 ` [PATCH 06/17] icu: fix buildpaths QA issue Hongxu Jia
2016-03-28 8:18 ` [PATCH 07/17] tcl: fix buildpath " Hongxu Jia
2016-03-28 8:18 ` [PATCH 08/17] python2/3: " Hongxu Jia
2016-03-28 8:18 ` [PATCH 09/17] bbclass distutils/distutils3: fix .pyc/.pyo buildpath Hongxu Jia
2016-03-28 8:18 ` [PATCH 10/17] bbclass distutils/distutils3/setuptools/setuptools3: clean up DISTUTILS_INSTALL_ARGS Hongxu Jia
2016-03-28 8:18 ` [PATCH 11/17] python-setuptools/python3-setuptools: use old-style install Hongxu Jia
2016-03-28 8:18 ` [PATCH 12/17] python3-pip: " Hongxu Jia
2016-03-28 8:18 ` [PATCH 13/17] waf.bbclass: support do patch on extracted files Hongxu Jia
2016-03-28 8:18 ` [PATCH 14/17] python-pycairo: fix buildpath QA issue Hongxu Jia
2016-03-28 8:18 ` [PATCH 15/17] openssl: " Hongxu Jia
2016-03-28 8:19 ` [PATCH 16/17] epiphany: fix buildpaths " Hongxu Jia
2016-03-28 8:19 ` [PATCH 17/17] ifupdown: fix do_compile failed while GCCVERSION = "4.9%" Hongxu Jia
2016-03-30 8:06 ` [PATCH V7 00/17] fix buildpaths QA issue && dbp package source generation Hongxu Jia
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=56FB65CE.1050908@windriver.com \
--to=hongxu.jia@windriver.com \
--cc=mark.hatle@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.org \
--cc=ross.burton@intel.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