From: Tom Rini <tom_rini@mentor.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH, RFC] Add linux-libc-headers-native, make it default dep for native
Date: Tue, 08 Jun 2010 07:36:53 -0700 [thread overview]
Message-ID: <4C0E5585.8010907@mentor.com> (raw)
In-Reply-To: <AANLkTilJrzCr73GBdsGFgxQl4Gn7FAGj3Aytx1IrzYpS@mail.gmail.com>
Frans Meulenbroeks wrote:
> 2010/6/7 Tom Rini <tom_rini@mentor.com>:
>> On some host distributions the provided linux kernel headers are too old
>> to compile utilities we need[1]. Given that we need these utilities to
>> run things on the target the best solution is to provide
>> linux-libc-headers-native. Rather than get things into an inconsistent
>> state, we make linux-libc-headers-native be a default dependency.
>>
>> [1]: A prime example of this would be mtd-utils-native and UBI
>
> I'd say this is heading in the totally wrong direction.
>
> Target code should not depend on host headers.
> And if you need the target headers, you should depend on and use
> linux-libc-headers.
>
> I guess mtd-utils-native is used to make an mtd image for the target
> and as such I would expect it to use the target headers.
>
> What would be the difference between linux-libc-headers and
> linux-libc-headers-native in the first place?
> (and if there is a difference, I think a better package name would be
> linux-libc-headers-cross).
As Khem said, you're thinking in the wrong direction here. Target stuff
which needs the headers get the headers via linux-libc-headers. The
problem is runs on the host tools that generate things for the target.
> Btw if say mtd-utils-native needs kernel headers to access host
> functionality using headers for a different kernel version seems to be
> a no-no either.
mtd-utils is depending on OK to be exported by the kernel information to
know how to make a UBI image. And again, for the target this just works.
> PS: which distributions/distribution versions/kernel versions do have
> this problem?
> Ubuntu 8.04 (which has a 2.6.24 kernel) does not seem to exhibit this problem).
RHEL4.
--
Tom Rini
Mentor Graphics Corporation
next prev parent reply other threads:[~2010-06-08 14:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-07 19:33 [PATCH, RFC] Add linux-libc-headers-native, make it default dep for native Tom Rini
2010-06-07 21:21 ` Khem Raj
2010-06-07 21:31 ` Chris Larson
2010-06-08 0:19 ` Khem Raj
2010-06-08 6:36 ` Frans Meulenbroeks
2010-06-08 14:04 ` Khem Raj
2010-06-08 14:36 ` Tom Rini [this message]
2010-06-09 6:45 ` Frans Meulenbroeks
2010-06-09 14:51 ` Tom Rini
2010-06-15 17:48 ` Tom Rini
2010-06-15 23:30 ` Leon Woestenberg
2010-06-16 2:06 ` Tom Rini
2010-06-16 7:36 ` Frans Meulenbroeks
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=4C0E5585.8010907@mentor.com \
--to=tom_rini@mentor.com \
--cc=openembedded-devel@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