From: "David Nyström" <david.nystrom@enea.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: McClintock Matthew-B29882 <B29882@freescale.com>,
"yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: [meta-fsl-ppc][PATCH 2/2] fsl.conf: Let linux-qoriq-sdk-headers-nativesdk provide linux-libc-headers-nativesdk
Date: Mon, 20 Aug 2012 09:23:44 +0200 [thread overview]
Message-ID: <5031E600.8030208@enea.com> (raw)
In-Reply-To: <CAMKF1sq=wRkTBAcUkLQhbv0QX6rCAA3cb8S39hYSAM4knfqcbw@mail.gmail.com>
On 08/14/2012 09:26 PM, Khem Raj wrote:
> On Tue, Aug 14, 2012 at 12:49 AM, David Nyström <david.nystrom@enea.com> wrote:
>> Hi, it looks like this was merged to the denzil branch, and
>> PREFERRED_PROVIDER_linux-libc-headers-nativesdk was moved back to
>> distro.conf.
>> Any reason for this ?
> why do you want nativesdk headers to come from BSP its a fsl-ppc bsp I
> dont expect it to have something special for SDK hosts which are
> usually x86 ? afterall these are for
> the SDK host and not for target. Moreover it means that this BSP will
> not play in the multi BSP environment something you never want.
My main concern is that meta-toolchain uses linux-libc-headers-nativesdk
for the meta-toolchain
tarball build, i.e. the meta-toolchain API may differ from the on-target
API in regards to kernel-headers, no ?
This might very well be true if kernel version of
linux-libc-headers-nativesdk != linux-libc-headers
Br,
David
next prev parent reply other threads:[~2012-08-20 7:21 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-06 4:51 [meta-fsl-ppc][PATCH 1/2] machines: Dont lock linux-libc-headers-nativesdk preferred provider Khem Raj
2012-07-06 4:51 ` [meta-fsl-ppc][PATCH 2/2] fsl.conf: Let linux-qoriq-sdk-headers-nativesdk provide linux-libc-headers-nativesdk Khem Raj
2012-07-06 10:49 ` David Nyström
2012-07-06 12:52 ` David Nyström
2012-07-06 15:47 ` McClintock Matthew-B29882
2012-07-06 22:35 ` David Nyström
2012-07-06 22:39 ` McClintock Matthew-B29882
2012-08-14 7:49 ` David Nyström
2012-08-14 19:26 ` Khem Raj
2012-08-16 19:37 ` McClintock Matthew-B29882
2012-08-17 5:12 ` Khem Raj
2012-08-17 5:51 ` McClintock Matthew-B29882
2012-08-20 7:23 ` David Nyström [this message]
2012-08-20 16:45 ` Khem Raj
2012-08-20 18:13 ` McClintock Matthew-B29882
2012-08-20 19:27 ` Khem Raj
2012-08-20 19:43 ` McClintock Matthew-B29882
2012-08-20 19:50 ` McClintock Matthew-B29882
2012-08-21 14:54 ` David Nyström
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=5031E600.8030208@enea.com \
--to=david.nystrom@enea.com \
--cc=B29882@freescale.com \
--cc=raj.khem@gmail.com \
--cc=yocto@yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.