All of lore.kernel.org
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] glib-2.0: remove old glib-2.0-native recipes
Date: Fri, 09 Apr 2010 09:51:31 +0200	[thread overview]
Message-ID: <hpmma4$s8u$2@dough.gmane.org> (raw)
In-Reply-To: <1270761657-18322-1-git-send-email-ospite@studenti.unina.it>

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

On 08-04-10 23:20, Antonio Ospite wrote:
> Having these around can cause some conflict in recipes depending on
> recent glib-2.0-native, see [1].
> 
> What can happen is that, when no preferred versions are set (like in
> DISTRO=minimal), bitbake picks up an older -native recipe even if a more
> recent one using the BBCLASSEXTEND = "native" mechanism exists.

If that's the actual problem, leave the recipes alone and set a
PREFERRED_VERSION in your distro.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFLvtyCMkyGM64RGpERAlB6AKCzEAsBCP7w2pvTjaSYwYtVSgiphwCdFL85
5bgqOlpaZNMnGEaagMpH/9g=
=iWC6
-----END PGP SIGNATURE-----




  parent reply	other threads:[~2010-04-09  7:55 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-03 15:17 gtk+-native-2.20.0-r8.0 fails in do_configure Antonio Ospite
2010-04-03 18:17 ` Marcin Juszkiewicz
2010-04-06  9:58   ` Antonio Ospite
2010-04-08  9:22     ` Antonio Ospite
2010-04-08  9:54       ` Koen Kooi
2010-04-08 14:21         ` Antonio Ospite
2010-04-08 21:20           ` [PATCH] glib-2.0: remove old glib-2.0-native recipes Antonio Ospite
2010-04-08 21:33             ` Mike Westerhof
2010-04-08 22:50               ` Tom Rini
2010-04-09  7:51             ` Koen Kooi [this message]
2010-04-09 10:32               ` Michael 'Mickey' Lauer
2010-04-09 19:21               ` Antonio Ospite
2010-04-08 14:11   ` gtk+-native-2.20.0-r8.0 fails in do_configure Antonio Ospite
2010-04-08 14:15     ` Koen Kooi
2010-04-08 14:25       ` Antonio Ospite
2010-04-08 15:55         ` Koen Kooi

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='hpmma4$s8u$2@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.