Skip to contentSkip to conversation

external-toolchain: BR2_TOOLCHAIN_EXTERNAL_GLIBC includes eglibc

PATCH New Baruch Siach 2 participants 5 messages Sep 25, 2012

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 external-toolchain: BR2_TOOLCHAIN_EXTERNAL_GLIBC includes eglibc

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."

---
 toolchain/toolchain-external/Config.in |    6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)
toolchain/toolchain-external/Config.in +5 -1
index f86ed74..f7a84b2 100644
@@ -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
 
Signature · 1 line
1.7.10.4
#1 lore raw

PATCH 1/1 external-toolchain: BR2_TOOLCHAIN_EXTERNAL_GLIBC includes eglibc

Dear Baruch Siach,

toolchain/toolchain-external/Config.in config BR2_TOOLCHAIN_EXTERNAL_CUSTOM_UCLIBC · line 672

Quoted 3 lines · Baruch Siach
toolchain/toolchain-external/Config.in +3 -0
+	  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

Signature · 4 lines
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
#2 lore raw

PATCH 1/1 external-toolchain: BR2_TOOLCHAIN_EXTERNAL_GLIBC includes eglibc

Hi Thomas,

Quoted 14 lines · Thomas Petazzoni

Dear Baruch Siach,

toolchain/toolchain-external/Config.in config BR2_TOOLCHAIN_EXTERNAL_CUSTOM_UCLIBC · line 672

Quoted 3 lines · Baruch Siach
toolchain/toolchain-external/Config.in +3 -0
+	  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.

Quoted 5 lines

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

Signature · 3 lines
     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 -
#3 lore raw

PATCH 1/1 external-toolchain: BR2_TOOLCHAIN_EXTERNAL_GLIBC includes eglibc

Dear Baruch Siach,

Quoted 3 lines · Baruch Siach

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

Signature · 4 lines
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
#4 lore raw

PATCH 1/1 external-toolchain: BR2_TOOLCHAIN_EXTERNAL_GLIBC includes eglibc

Hi Thomas,

Quoted 4 lines · Thomas Petazzoni

Dear Baruch Siach,

On Tue, 25 Sep 2012 10:33:30 +0200, Baruch Siach wrote:

Quoted 8 lines
Quoted 3 lines

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

Signature · 3 lines
     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 -