From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] external-toolchain: BR2_TOOLCHAIN_EXTERNAL_GLIBC includes eglibc
Date: Tue, 25 Sep 2012 15:46:31 +0200 [thread overview]
Message-ID: <20120925134631.GE4439@tarshish> (raw)
In-Reply-To: <20120925103952.20f4d20a@skate>
Hi Thomas,
On Tue, Sep 25, 2012 at 10:39:52AM +0200, Thomas Petazzoni wrote:
> Dear Baruch Siach,
>
> On Tue, 25 Sep 2012 10:33:30 +0200, Baruch Siach wrote:
>
> > This is exactly what I meant to say, but the text surely needs to be clearer
> > as you suggest. What feature do you think we need to mention as minimal
> > requirements in the help text?
>
> I have no idea, since I have never looked at what eglibc provides in
> terms of configurability :) I guess Yann can give details on this, he
> is quite certainly a lot more aware than I am about what the eglibc
> options are.
Well, after a little thought, maybe we shouldn't get into configuration
details here and just say something general like: "Warning: using a toolchain
with eglibc configuration lacking key features (examples?) may result in build
failures, depending on your choice of packages."
baruch
--
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -
next prev parent reply other threads:[~2012-09-25 13:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-25 3:49 [Buildroot] [PATCH] external-toolchain: BR2_TOOLCHAIN_EXTERNAL_GLIBC includes eglibc Baruch Siach
2012-09-25 7:54 ` Thomas Petazzoni
2012-09-25 8:33 ` Baruch Siach
2012-09-25 8:39 ` Thomas Petazzoni
2012-09-25 13:46 ` Baruch Siach [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-09-24 19:38 Baruch Siach
2012-09-24 20:26 ` Yann E. MORIN
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=20120925134631.GE4439@tarshish \
--to=baruch@tkos.co.il \
--cc=buildroot@busybox.net \
/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