All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 2/2] tclibc-uclibc.inc: Append -uclibc only to target recipes
Date: Mon, 16 May 2011 14:50:41 +0100	[thread overview]
Message-ID: <1305553841.3424.76.camel@rex> (raw)
In-Reply-To: <982B5C11-301B-48C4-91A9-E73BF47FEF8D@dominion.thruhere.net>

On Mon, 2011-05-16 at 15:11 +0200, Koen Kooi wrote:
> Op 16 mei 2011, om 13:41 heeft Richard Purdie het volgende geschreven:
> 
> > On Mon, 2011-05-16 at 02:55 -0700, Khem Raj wrote:
> >> On Sun, May 15, 2011 at 11:58 PM, Koen Kooi <koen@dominion.thruhere.net> wrote:
> >>> 
> >>> Op 16 mei 2011, om 08:04 heeft Khem Raj het volgende geschreven:
> >>> 
> >>>> Do not define DEPLOY_DIR_IMAGE
> >>>> Append -uclibc to STAGING_DIR_TARGET only for target recipe and cross
> >>>> recipes
> >>>> Append -uclibc to STAGING_DIR_HOST only for target recipes.
> >>>> 
> >>>> These changes make sure that we still share the native sysroot
> >>> 
> >>> I still stay we append tclibc unconditionally.
> >> 
> >> yes thats would simplify things if we agree to use TCLIBC in bitbake.conf
> > 
> > We can't depend on TCLIBC in bitbake.conf since someone still has the
> > option of not using the standard configuration boilerplate we're
> > providing.
> 
> So we can't add TCLIBC ??= eglibc to bitbake.conf?

No, I can just see the bug reports for uclibc building in a directory
called XXX-eglibc as the user had only set the PREFERRED_PROVIDER
variables.

Cheers,

Richard




  reply	other threads:[~2011-05-16 13:53 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-16  6:04 [PATCH 0/2] Adjust default distrovars Khem Raj
2011-05-16  6:04 ` [PATCH 1/2] default-distrovars.inc: Do not add DISTRO_EXTRA_RDEPENDS and DISTRO_EXTRA_RRECOMMENDS Khem Raj
2011-05-16  6:04 ` [PATCH 2/2] tclibc-uclibc.inc: Append -uclibc only to target recipes Khem Raj
2011-05-16  6:58   ` Koen Kooi
2011-05-16  9:55     ` Khem Raj
2011-05-16 11:41       ` Richard Purdie
2011-05-16 13:11         ` Koen Kooi
2011-05-16 13:50           ` Richard Purdie [this message]
2011-05-16 15:43             ` Koen Kooi
2011-05-17  0:13   ` Richard Purdie
2011-05-17  9:17     ` Phil Blundell
2011-05-17  9:34       ` Richard Purdie
2011-05-17  9:44         ` Phil Blundell
2011-05-17 14:31           ` Richard Purdie
2011-05-17 14:40             ` Phil Blundell
2011-05-18  5:36           ` Khem Raj
2011-05-18  5:49     ` Khem Raj
2011-05-18  7:49     ` Khem Raj
2011-05-18  7:57       ` Richard Purdie
2011-05-18  8:12         ` Khem Raj
2011-05-18  8:47           ` Koen Kooi
2011-05-18  9:55             ` Khem Raj
2011-05-18  8:48         ` Frans Meulenbroeks
2011-05-18 10:09           ` Richard Purdie
2011-05-20  1:10 ` [PATCH 0/2] Adjust default distrovars Saul Wold

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=1305553841.3424.76.camel@rex \
    --to=richard.purdie@linuxfoundation.org \
    --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.