* [Buildroot] [PATCH] external-toolchain: BR2_TOOLCHAIN_EXTERNAL_GLIBC includes eglibc
@ 2012-09-25 3:49 Baruch Siach
2012-09-25 7:54 ` Thomas Petazzoni
0 siblings, 1 reply; 7+ messages in thread
From: Baruch Siach @ 2012-09-25 3:49 UTC (permalink / raw)
To: buildroot
Yann E. MORIN says:
"Although eglibc can be configured to include/exclude parts of the
features, it seems to not be in wide use, if at all."
Acked-by: Yann E. MORIN <yann.morin.1998@free.fr>
Signed-off-by: Baruch Siach <baruch@tkos.co.il>
---
toolchain/toolchain-external/Config.in | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/toolchain/toolchain-external/Config.in b/toolchain/toolchain-external/Config.in
index f86ed74..f7a84b2 100644
--- a/toolchain/toolchain-external/Config.in
+++ b/toolchain/toolchain-external/Config.in
@@ -664,8 +664,12 @@ config BR2_TOOLCHAIN_EXTERNAL_CUSTOM_UCLIBC
select BR2_TOOLCHAIN_HAS_SHADOW_PASSWORDS
config BR2_TOOLCHAIN_EXTERNAL_CUSTOM_GLIBC
- bool "glibc"
+ bool "glibc/eglibc"
select BR2_TOOLCHAIN_EXTERNAL_GLIBC
+ help
+ Note: eglibc is a variant of glibc that (among other things) can be
+ configured to exclude parts of its features. This capability is
+ currently not supported.
endchoice
--
1.7.10.4
^ permalink raw reply related [flat|nested] 7+ messages in thread* [Buildroot] [PATCH] external-toolchain: BR2_TOOLCHAIN_EXTERNAL_GLIBC includes eglibc
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
0 siblings, 1 reply; 7+ messages in thread
From: Thomas Petazzoni @ 2012-09-25 7:54 UTC (permalink / raw)
To: buildroot
Dear Baruch Siach,
On Tue, 25 Sep 2012 05:49:53 +0200, Baruch Siach wrote:
> + Note: eglibc is a variant of glibc that (among other things) can be
> + configured to exclude parts of its features. This capability is
> + currently not supported.
This note makes no sense in the context of external toolchains: the C
library is already compiled into the external toolchain, so it's the
responsibility of the person building the external toolchain to know
how to configure eglibc. The fact that we don't support eglibc
configuration in Buildroot doesn't make much sense.
Or, if you want to mean that we don't support eglibc toolchains that
have been configured to leave out certain features (such as IPv6
support for example), then it should be said in a different way, such
as: "We only support eglibc toolchains providing this, that and this
other feature".
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
^ permalink raw reply [flat|nested] 7+ messages in thread
* [Buildroot] [PATCH] external-toolchain: BR2_TOOLCHAIN_EXTERNAL_GLIBC includes eglibc
2012-09-25 7:54 ` Thomas Petazzoni
@ 2012-09-25 8:33 ` Baruch Siach
2012-09-25 8:39 ` Thomas Petazzoni
0 siblings, 1 reply; 7+ messages in thread
From: Baruch Siach @ 2012-09-25 8:33 UTC (permalink / raw)
To: buildroot
Hi Thomas,
On Tue, Sep 25, 2012 at 09:54:42AM +0200, Thomas Petazzoni wrote:
> Dear Baruch Siach,
>
> On Tue, 25 Sep 2012 05:49:53 +0200, Baruch Siach wrote:
>
> > + Note: eglibc is a variant of glibc that (among other things) can be
> > + configured to exclude parts of its features. This capability is
> > + currently not supported.
>
> This note makes no sense in the context of external toolchains: the C
> library is already compiled into the external toolchain, so it's the
> responsibility of the person building the external toolchain to know
> how to configure eglibc. The fact that we don't support eglibc
> configuration in Buildroot doesn't make much sense.
>
> Or, if you want to mean that we don't support eglibc toolchains that
> have been configured to leave out certain features (such as IPv6
> support for example), then it should be said in a different way, such
> as: "We only support eglibc toolchains providing this, that and this
> other feature".
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?
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 -
^ permalink raw reply [flat|nested] 7+ messages in thread* [Buildroot] [PATCH] external-toolchain: BR2_TOOLCHAIN_EXTERNAL_GLIBC includes eglibc
2012-09-25 8:33 ` Baruch Siach
@ 2012-09-25 8:39 ` Thomas Petazzoni
2012-09-25 13:46 ` Baruch Siach
0 siblings, 1 reply; 7+ messages in thread
From: Thomas Petazzoni @ 2012-09-25 8:39 UTC (permalink / raw)
To: buildroot
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.
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
^ permalink raw reply [flat|nested] 7+ messages in thread
* [Buildroot] [PATCH] external-toolchain: BR2_TOOLCHAIN_EXTERNAL_GLIBC includes eglibc
2012-09-25 8:39 ` Thomas Petazzoni
@ 2012-09-25 13:46 ` Baruch Siach
0 siblings, 0 replies; 7+ messages in thread
From: Baruch Siach @ 2012-09-25 13:46 UTC (permalink / raw)
To: buildroot
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 -
^ permalink raw reply [flat|nested] 7+ messages in thread
* [Buildroot] [PATCH] external-toolchain: BR2_TOOLCHAIN_EXTERNAL_GLIBC includes eglibc
@ 2012-09-24 19:38 Baruch Siach
2012-09-24 20:26 ` Yann E. MORIN
0 siblings, 1 reply; 7+ messages in thread
From: Baruch Siach @ 2012-09-24 19:38 UTC (permalink / raw)
To: buildroot
Signed-off-by: Baruch Siach <baruch@tkos.co.il>
---
toolchain/toolchain-external/Config.in | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/toolchain/toolchain-external/Config.in b/toolchain/toolchain-external/Config.in
index f86ed74..911fea4 100644
--- a/toolchain/toolchain-external/Config.in
+++ b/toolchain/toolchain-external/Config.in
@@ -664,7 +664,7 @@ config BR2_TOOLCHAIN_EXTERNAL_CUSTOM_UCLIBC
select BR2_TOOLCHAIN_HAS_SHADOW_PASSWORDS
config BR2_TOOLCHAIN_EXTERNAL_CUSTOM_GLIBC
- bool "glibc"
+ bool "glibc/eglibc"
select BR2_TOOLCHAIN_EXTERNAL_GLIBC
endchoice
--
1.7.10.4
^ permalink raw reply related [flat|nested] 7+ messages in thread
* [Buildroot] [PATCH] external-toolchain: BR2_TOOLCHAIN_EXTERNAL_GLIBC includes eglibc
2012-09-24 19:38 Baruch Siach
@ 2012-09-24 20:26 ` Yann E. MORIN
0 siblings, 0 replies; 7+ messages in thread
From: Yann E. MORIN @ 2012-09-24 20:26 UTC (permalink / raw)
To: buildroot
Baruch, All,
On Monday 24 September 2012 21:38:52 Baruch Siach wrote:
> Signed-off-by: Baruch Siach <baruch@tkos.co.il>
> ---
> toolchain/toolchain-external/Config.in | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/toolchain/toolchain-external/Config.in b/toolchain/toolchain-external/Config.in
> index f86ed74..911fea4 100644
> --- a/toolchain/toolchain-external/Config.in
> +++ b/toolchain/toolchain-external/Config.in
> @@ -664,7 +664,7 @@ config BR2_TOOLCHAIN_EXTERNAL_CUSTOM_UCLIBC
> select BR2_TOOLCHAIN_HAS_SHADOW_PASSWORDS
>
> config BR2_TOOLCHAIN_EXTERNAL_CUSTOM_GLIBC
> - bool "glibc"
> + bool "glibc/eglibc"
> select BR2_TOOLCHAIN_EXTERNAL_GLIBC
For all practical purposes, that's true.
Although eglibc can be configured to include/exclude parts of the features,
it seems to not be in wide use, if at all.
So, I'd like that to be at least mentionned in the commit log, and maybe
as a help entry for BR2_TOOLCHAIN_EXTERNAL_CUSTOM_GLIBC.
With that:
Acked-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2012-09-25 13:46 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
-- strict thread matches above, loose matches on Subject: below --
2012-09-24 19:38 Baruch Siach
2012-09-24 20:26 ` Yann E. MORIN
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox