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: Thu, 06 May 2010 12:42:47 +0200 [thread overview]
Message-ID: <hru6f7$4qk$1@dough.gmane.org> (raw)
In-Reply-To: <1273140949-14699-1-git-send-email-sledz@dresearch.de>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 06-05-10 12:15, Steffen Sledz wrote:
> Signed-off-by: Steffen Sledz <sledz@dresearch.de>
> ---
> conf/distro/angstrom-2008.1.conf | 3 ++-
> 1 files changed, 2 insertions(+), 1 deletions(-)
>
> diff --git a/conf/distro/angstrom-2008.1.conf b/conf/distro/angstrom-2008.1.conf
> index 1df0c0b..760166b 100644
> --- a/conf/distro/angstrom-2008.1.conf
> +++ b/conf/distro/angstrom-2008.1.conf
> @@ -81,7 +81,8 @@ PREFERRED_VERSION_linux-handhelds-2.6 ?= "2.6.21-hh20"
> #KERNEL_INITRAMFS_PATH = "${KERNEL_INITRAMFS_DIR}/$(readlink ${KERNEL_INITRAMFS_DIR}initramfs-bootmenu-image-${MACHINE}.cpio.gz)"
>
> #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"
>
> #Prefer glibc 2.6 and uclibc 0.9.30, these have had the most testing.
> PREFERRED_VERSION_glibc ?= "2.9"
NACK, that creates undefined behaviour for multimachine builds.
Also, please remove the legacy staging behaviour from the
linux-libc-headers recipe you just pushed.
regards,
Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFL4p0mMkyGM64RGpERAug1AJ9uEHk3KtRBXbILlfAM9IKV8kPC2ACfQHF4
p8l5iA3z+D1L5x+17Yq/u+Y=
=rjzW
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2010-05-06 10:47 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 [this message]
2010-05-06 10:47 ` Steffen Sledz
2010-05-07 6:59 ` Steffen Sledz
2010-05-07 7:23 ` Koen Kooi
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='hru6f7$4qk$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.