All of lore.kernel.org
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: [RFC] Bring PREFERRED_LIBC to all distros
Date: Mon, 27 Apr 2009 17:33:31 +0200	[thread overview]
Message-ID: <gt4j8d$u5m$1@ger.gmane.org> (raw)
In-Reply-To: <20090427141943.GG18788@smtp.west.cox.net>

On 27-04-09 16:19, Tom Rini wrote:
> Hey all.  I've created a new branch, trini/add-libc-overrides which does
> the following:
> - Make every distro declare PREFERRED_LIBC, either outright or
>    overridable.

ACK on the idea, NACK on the implementation.

ANGSTROMLIBC is called ANGSTROMLIBC and not ANGSTROM_LIBC for a reason, 
since you can't pass env vars with underscores throught bitbake: 
http://lists.linuxtogo.org/pipermail/openembedded-devel/2008-December/007258.html

I've shown the PREFERRED_LIBC thing in the past to other OE core 
developers as an example of the mindless copy/paste/rename process in 
angstrom clones. Don't clone if you don't know what you are doing.

So please keep things you want to override in buildscripts (e.g. 
machine, libc, distro) underscore free :)

regards,

Koen




  parent reply	other threads:[~2009-04-27 15:38 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-27 14:19 [RFC] Bring PREFERRED_LIBC to all distros Tom Rini
2009-04-27 14:22 ` [RFC][PATCH] All distro conf files: Use PREFERRED_LIBC to pick or set your libc Tom Rini
2009-04-27 14:23   ` [RFC][PATCH] Add distro inc files for eglibc, glibc and uclibc Tom Rini
2009-04-27 14:23     ` [RFC][PATCH] All distros: Bring in conf/distro/include/${PREFERRED_LIBC}.inc Tom Rini
2009-04-27 14:24       ` [RFC][PATCH] glibc: In various old recipes add RPROVIDES virtual-libc-dev, bump PR Tom Rini
2009-04-27 15:33 ` Koen Kooi [this message]
2009-04-27 15:43   ` [RFC] Bring PREFERRED_LIBC to all distros Tom Rini
2009-04-27 16:45     ` Koen Kooi
2009-04-27 16:51       ` Tom Rini
2009-04-27 17:32         ` Philip Balister
2009-04-27 17:36           ` Tom Rini
2009-04-27 15:35 ` Otavio Salvador
2009-04-29 16:06   ` Tom Rini
2009-04-28 20:30 ` Khem Raj
2009-04-28 20:55   ` Tom Rini
2009-04-29  5:40     ` Koen Kooi
2009-04-29 16:12 ` Tom Rini
2009-04-29 23:25   ` Leon Woestenberg
2009-05-02 19:55   ` Mike (mwester)
2009-05-03 12:29     ` Leon Woestenberg
2009-05-03 16:53       ` Tom Rini
2009-05-10 19:47         ` Tom Rini
2009-05-10 21:03           ` Koen Kooi
2009-05-10 21:51             ` Tom Rini
2009-05-10 22:27               ` Otavio Salvador
2009-05-10 22:36                 ` Tom Rini
2009-05-11  7:03                   ` Koen Kooi
2009-05-11  8:07                     ` Richard Purdie
2009-05-11  8:27                       ` Graeme Gregory

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='gt4j8d$u5m$1@ger.gmane.org' \
    --to=k.kooi@student.utwente.nl \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=openembedded-devel@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.