Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] angstrom-2008: make PREFERRED_VERSION_linux-libc-headers a weak assignment
Date: Mon, 19 Apr 2010 22:01:55 +0200	[thread overview]
Message-ID: <hqicrj$dp9$1@dough.gmane.org> (raw)
In-Reply-To: <1271687665-23003-2-git-send-email-vjensen@gmx.de>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 19-04-10 16:34, Vitus Jensen wrote:
> 
> Signed-off-by: Vitus Jensen <vjensen@gmx.de>
> ---
>  conf/distro/angstrom-2008.1.conf |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
> 
> diff --git a/conf/distro/angstrom-2008.1.conf b/conf/distro/angstrom-2008.1.conf
> index 2b03e71..00f1a01 100644
> --- a/conf/distro/angstrom-2008.1.conf
> +++ b/conf/distro/angstrom-2008.1.conf
> @@ -81,7 +81,7 @@ 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"

NACK, there's is a good reason it's not soft assigned. Your hack to make
it machine specific is worse, since it means that other machines with
the same arch now get a "random" version.

What we can do is globally increase the version, which was planned
anyway. Does can need .32 or .33? I tested using llc .32 locally, but
hadn't pushed that change yet.

regards,

Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFLzLazMkyGM64RGpERAprHAJ4g/qIJ+2JTBX2dBV5j9qvXabB77ACghL2M
mkx8G87d5lGlBbJDbKaOSos=
=1pVK
-----END PGP SIGNATURE-----




  reply	other threads:[~2010-04-19 20:05 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-16 17:14 canutils Vitus Jensen
2010-04-16 17:15 ` [PATCH 1/2] libsocketcan: recipe to build pengutronix' libsocketcan (netlink interface) Vitus Jensen
2010-04-16 17:31   ` Koen Kooi
2010-04-16 19:28     ` Vitus Jensen
2010-04-16 20:35       ` Henning Heinold
2010-04-20  8:09     ` Vitus Jensen
2010-04-16 17:16 ` [PATCH 2/2] canutils: add new recipe Vitus Jensen
2010-04-19 14:34 ` canutils Vitus Jensen
2010-04-19 14:34   ` [PATCH] angstrom-2008: make PREFERRED_VERSION_linux-libc-headers a weak assignment Vitus Jensen
2010-04-19 20:01     ` Koen Kooi [this message]
2010-04-20  6:32       ` Vitus Jensen
2010-04-29 17:04       ` GNUtoo
2010-05-01 14:17 ` canutils Vitus Jensen
2010-05-01 14:22   ` [PATCH v2] libsocketcan: new recipe Vitus Jensen
2010-05-01 14:22     ` [PATCH v2] canutils: " Vitus Jensen
2010-05-07 10:18       ` Stefan Schmidt
2010-05-07 11:15         ` Koen Kooi
2010-05-16 20:26           ` Vitus Jensen
2010-05-21 14:38             ` [PATCH v3 1/3] libsocketcan: new recipes Vitus Jensen
2010-05-21 14:38               ` [PATCH v3 2/3] canutils: " Vitus Jensen
2010-05-21 14:38                 ` [PATCH v3 3/3] socketcan-utils-test: rconflicts with canutils Vitus Jensen
2010-05-21 20:39               ` [PATCH v3 1/3] libsocketcan: new recipes Khem Raj
2010-05-22 15:26                 ` Vitus Jensen
2010-05-07 10:17     ` [PATCH v2] libsocketcan: new recipe Stefan Schmidt

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='hqicrj$dp9$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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox