From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] angstrom-2008.1: use linux-libc-headers 2.6.24 for hipox machine
Date: Fri, 07 May 2010 09:23:32 +0200 [thread overview]
Message-ID: <hs0f5k$sl$1@dough.gmane.org> (raw)
In-Reply-To: <4BE3BA38.1010102@dresearch.de>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 07-05-10 08:59, Steffen Sledz wrote:
>>> #This is unrelated to the kernel version, but userspace apps (e.g. HAL) require a recent version to build against
>>> -PREFERRED_VERSION_linux-libc-headers = "2.6.31"
>>> +PREFERRED_VERSION_linux-libc-headers ?= "2.6.31"
>>> +PREFERRED_VERSION_linux-libc-headers_hipox ?= "2.6.24"
>>
>> NACK, that creates undefined behaviour for multimachine builds.
>
> -PREFERRED_VERSION_linux-libc-headers = "2.6.31"
> +PREFERRED_VERSION_linux-libc-headers = "2.6.31"
> +PREFERRED_VERSION_linux-libc-headers_hipox = "2.6.24"
>
> Is this better?
No, it still changes the headers for one machine, which leads to
undefined behaviour for other machines using the same arch.
Any solution that doesn't mark *all* packages as machine specific for
hipox is going to cause that behaviour.
regards,
Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFL47/0MkyGM64RGpERAmtKAJ4i6iHnKPD3Jhc2KGiFtQzj1g2kVQCeP8aa
fthjVFJAj6ahKSlqhgHA3yk=
=v8r3
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2010-05-07 7:27 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-05 9:36 linux vs. linux-libc-headers? Steffen Sledz
2010-05-05 9:42 ` Graeme Gregory
2010-05-05 10:00 ` Steffen Sledz
2010-05-05 10:05 ` Phil Blundell
2010-05-05 14:50 ` Steffen Sledz
2010-05-06 10:15 ` [PATCH] angstrom-2008.1: use linux-libc-headers 2.6.24 for hipox machine Steffen Sledz
2010-05-06 10:42 ` Koen Kooi
2010-05-06 10:47 ` Steffen Sledz
2010-05-07 6:59 ` Steffen Sledz
2010-05-07 7:23 ` Koen Kooi [this message]
2010-05-07 7:35 ` Steffen Sledz
2010-05-10 7:36 ` Steffen Sledz
2010-05-10 8:34 ` Koen Kooi
2010-05-10 16:46 ` Tom Rini
2010-05-06 12:03 ` Steffen Sledz
2010-05-07 9:03 ` linux vs. linux-libc-headers? Phil Blundell
2010-05-10 9:15 ` Steffen Sledz
2010-05-12 10:10 ` Phil Blundell
2010-05-10 14:53 ` Kernel Headers Quality Issue (was: linux vs. linux-libc-headers?) Thilo Fromm
2010-05-10 16:55 ` Tom Rini
2010-05-10 19:00 ` Khem Raj
2010-05-14 9:25 ` Kernel Headers Quality Issue Thilo Fromm
2010-05-14 13:05 ` Phil Blundell
2010-05-11 7:19 ` Thilo Fromm
2010-05-10 19:14 ` Kernel Headers Quality Issue (was: linux vs. linux-libc-headers?) Tom Rini
2010-05-11 7:42 ` Kernel Headers Quality Issue Steffen Sledz
2010-05-11 14:27 ` Tom Rini
2010-05-12 6:02 ` Steffen Sledz
2010-05-12 15:23 ` Tom Rini
2010-05-12 16:53 ` Mark Brown
2010-05-13 11:40 ` Phil Blundell
2010-05-14 9:59 ` Thilo Fromm
2010-05-14 10:25 ` Phil Blundell
2010-05-14 11:40 ` Thilo Fromm
2010-05-14 12:38 ` Phil Blundell
2010-05-18 0:14 ` Mark Brown
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='hs0f5k$sl$1@dough.gmane.org' \
--to=k.kooi@student.utwente.nl \
--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 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.