From: Jamie Lenehan <lenehan@twibble.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: uclibc 0.9.29 recipe
Date: Wed, 16 May 2007 13:13:29 +1000 [thread overview]
Message-ID: <20070516031329.GA5205@twibble.org> (raw)
In-Reply-To: <46461D72.4020206@dominion.kabel.utwente.nl>
On Sat, May 12, 2007 at 10:02:58PM +0200, Koen Kooi wrote:
[...]
> I'll add it once I solved the linux-libc-headers problems. Machine and distro maintainers
> need to provide their parts of the uclibc configs to make it usefull, though.
Do we really need different distro based settings? It's always been a
bit annoying that some things will build with uclibc for one build
but not another due to differing uclibc settings - things are a lot
easier if there's only a single configuration.
For now I'd like to see a
mtn -e mv uclibc-0.9.29/angstrom/uClibc.distro uclibc-0.9.29/uClibc.distro
and then only add distro based configuration if it turns out to be
really needed by some distro. This'll also gives us a default
configuration for people using other distros.
--
Jamie Lenehan <lenehan@twibble.org>
next prev parent reply other threads:[~2007-05-16 3:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-12 19:21 uclibc 0.9.29 recipe Koen Kooi
2007-05-12 19:54 ` Lorn Potter
2007-05-12 20:02 ` Koen Kooi
2007-05-12 21:04 ` Koen Kooi
2007-05-13 16:45 ` Leon Woestenberg
2007-05-13 16:55 ` Koen Kooi
2007-05-13 21:39 ` Leon Woestenberg
2007-05-14 12:30 ` Koen Kooi
2007-05-12 21:19 ` minimal-image.bb Stelios Koroneos
2007-05-13 14:35 ` minimal-image.bb Rolf Leggewie
2007-05-15 8:10 ` minimal-image.bb Stelios Koroneos
2007-05-15 9:59 ` minimal-image.bb Rolf Leggewie
2007-05-16 3:13 ` Jamie Lenehan [this message]
2007-05-16 7:26 ` uclibc 0.9.29 recipe Leon Woestenberg
2007-05-16 7:41 ` Koen Kooi
2007-05-16 5:16 ` uclibc 0.9.29 & SYS_SIGLIST Jamie Lenehan
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=20070516031329.GA5205@twibble.org \
--to=lenehan@twibble.org \
--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