All of lore.kernel.org
 help / color / mirror / Atom feed
From: Phil Blundell <pb@pbcl.net>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: RDEPENDS_${PN} and virtclass-native
Date: Thu, 26 May 2011 11:15:42 +0100	[thread overview]
Message-ID: <1306404942.2525.299.camel@phil-desktop> (raw)
In-Reply-To: <BANLkTinUDhgtYgShemq_3vNuTHkOuCWdug@mail.gmail.com>

On Wed, 2011-05-25 at 16:08 -0700, Khem Raj wrote:
> while we are talking about fixing native.bbclass on a different
> tangent. I think overrides is another thing we need to fix
> specially libc overrides. When a recipe inherits
> native,cross, or nativesdk then we have to change
> the libc override to be always libc-glibc (unless one
> is building on a box which is running uclibc)

Just forcing "libc-glibc" on for native packages doesn't seem like the
right answer.  As well as the (perhaps unlikely) situation where the
build host is running uclibc, it might be a Darwin or Cygwin host which
doesn't use glibc at all.

I guess this is another reason why libc-* overrides should be used
sparingly :-}

p.





  reply	other threads:[~2011-05-26 10:18 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-25 17:01 RDEPENDS_${PN} and virtclass-native Phil Blundell
2011-05-25 17:03 ` Chris Larson
2011-05-25 23:02 ` Richard Purdie
2011-05-25 23:08   ` Khem Raj
2011-05-26 10:15     ` Phil Blundell [this message]
2011-05-26  0:00   ` Richard Purdie
2011-05-26  0:11     ` Chris Larson
2011-05-26  0:59       ` Richard Purdie
2011-05-31 23:04         ` Richard Purdie
2011-05-26 10:27 ` Phil Blundell
2011-05-31 11:29   ` [PATCH] prelink: remove dependency on transfig-native Phil Blundell
2011-05-31 11:46     ` Richard Purdie

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=1306404942.2525.299.camel@phil-desktop \
    --to=pb@pbcl.net \
    --cc=openembedded-core@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.