All of lore.kernel.org
 help / color / mirror / Atom feed
From: "David Nyström" <david.nystrom@enea.com>
To: McClintock Matthew-B29882 <B29882@freescale.com>
Cc: "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: Tue, 21 Aug 2012 16:54:06 +0200	[thread overview]
Message-ID: <5033A10E.1030000@enea.com> (raw)
In-Reply-To: <CAEsOVNfBgOGgmZm4BehTAm28v703d7Ao9ehkE2GD+dwxKswtOw@mail.gmail.com>

On 08/20/2012 09:50 PM, McClintock Matthew-B29882 wrote:
> Adding David back...
>
> -M
>
> On Mon, Aug 20, 2012 at 2:42 PM, Matthew McClintock <msm@freescale.com> wrote:
>> On Mon, Aug 20, 2012 at 2:27 PM, Khem Raj <raj.khem@gmail.com> wrote:
>>>> I just checked and we do have a few obscure bits in our kernel tree's
>>>> header files. Nothing that 99.9% would use but it seems reasonable to
>>>> include these...
>>> Do you want applications for sdk host to be built using these obscure bits ?
>>> if yes I would like to know why?
>>>
>>> since then you are creating a scenariou where nativesdk is dependent on target
>>> kernel and we need to fix it so that nativesdk can be common again.
>>>
>>> if patches you are carrying are good for nativesdk headers can they be made
>>> available for other kernels like linux-yocto e.g. ?
>>>
>>> right now if we do this we are pretty much saying fsl machine layer can really
>>> not mix with other BSPs. Many people use yocto commonly on more than one kind
>>> of CPU and this does not scale.
>> Hmm I think I was just confused. We don't need any modifications for
>> the headers for nativesdk foo (that is the x86 tools in
>> meta-toolchain).
>>
>> So, I think everything is OK as is.. if you look at meta-toolchain you
>> will see it includes our kernel's headers for cross compiling.
>>
>> -M

Oh, sorry for the misunderstanding

I was under the impression that linux-libc-headers-nativesdk was 
installed under
/opt/poky/1.2/sysroots/<target-sysroot>/..., which it obviously is not.

Br,
David


      reply	other threads:[~2012-08-21 14:52 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
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 [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=5033A10E.1030000@enea.com \
    --to=david.nystrom@enea.com \
    --cc=B29882@freescale.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.