From: Jonathan Liu <net147@gmail.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] kernel-devsrc: avoid splitting debug info
Date: Thu, 05 Mar 2015 06:56:15 +1100 [thread overview]
Message-ID: <54F7635F.6060403@gmail.com> (raw)
In-Reply-To: <1425487748.26813.105.camel@linuxfoundation.org>
Hi Richard,
On 5/03/2015 3:49 AM, Richard Purdie wrote:
> On Wed, 2015-03-04 at 00:31 +1100, Jonathan Liu wrote:
>> This fixes "QA Issue: non debug package contains .debug directory"
>> for some kernels.
>>
>> Signed-off-by: Jonathan Liu <net147@gmail.com>
>> ---
>> meta/recipes-kernel/linux/kernel-devsrc.bb | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/meta/recipes-kernel/linux/kernel-devsrc.bb b/meta/recipes-kernel/linux/kernel-devsrc.bb
>> index e36de1b..c3cad05 100644
>> --- a/meta/recipes-kernel/linux/kernel-devsrc.bb
>> +++ b/meta/recipes-kernel/linux/kernel-devsrc.bb
>> @@ -72,3 +72,4 @@ do_install[lockfiles] = "${TMPDIR}/kernel-scripts.lock"
>> PACKAGES = "kernel-devsrc"
>> FILES_${PN} = "${KERNEL_SRC_PATH}"
>> RDEPENDS_${PN} = "bc"
>> +INHIBIT_PACKAGE_DEBUG_SPLIT = "1"
> Why would your kernel source directory contain built binaries? I guess
> I'd like to understand more about what "some kernels" are doing
> differently.
>
> Cheers,
>
> Richard
>
The sources don't contain built binaries. It looks like there is an
issue somewhere in the kernel sources that needs fixing.
Please disregard this patch for now.
Regards,
Jonathan
prev parent reply other threads:[~2015-03-04 19:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-03 13:31 [PATCH] kernel-devsrc: avoid splitting debug info Jonathan Liu
2015-03-04 16:49 ` Richard Purdie
2015-03-04 19:56 ` Jonathan Liu [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=54F7635F.6060403@gmail.com \
--to=net147@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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