sconeserver: Can't be built with uClibc.
PATCH v2 1/1 sconeserver: Can't be built with uClibc.
From: Sonic Zhang <[email protected]>
General shadow password file API such as getspnam is not supported in uClibc.
--- package/sconeserver/Config.in | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-)
package/sconeserver/Config.in +3 -2
@@ -2,6 +2,7 @@ menuconfig BR2_PACKAGE_SCONESERVER bool "sconeserver" depends on BR2_INSTALL_LIBSTDCPP depends on BR2_TOOLCHAIN_HAS_THREADS + depends on !BR2_TOOLCHAIN_USES_UCLIBC select BR2_PACKAGE_PCRE help Sconeserver is a modular, object-orientated and extremely versatile
@@ -92,5 +93,5 @@ comment "ui module requires X.org" endif # BR2_PACKAGE_SCONESERVER -comment "sconeserver needs a toolchain w/ C++, threads" - depends on !(BR2_INSTALL_LIBSTDCPP && BR2_TOOLCHAIN_HAS_THREADS) +comment "sconeserver needs a non-uClibc toolchain w/ C++, threads" + depends on !(BR2_INSTALL_LIBSTDCPP && BR2_TOOLCHAIN_HAS_THREADS) || BR2_TOOLCHAIN_USES_UCLIBC
Signature · 1 line
1.7.9.5
PATCH v2 1/1 sconeserver: Can't be built with uClibc.
Hi Sonic,
Quoted 14 lines · Sonic Zhang
From: Sonic Zhang <[email protected]>
General shadow password file API such as getspnam is not supported in uClibc.
Signed-off-by Sonic Zhang <[email protected]>--- package/sconeserver/Config.in | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-)package/sconeserver/Config.in +0
-0
package/sconeserver/Config.in menuconfig BR2_PACKAGE_SCONESERVER · line 5
Quoted 4 lines
package/sconeserver/Config.in +1
-0@@ -2,6 +2,7 @@ menuconfig BR2_PACKAGE_SCONESERVER bool "sconeserver" depends on BR2_INSTALL_LIBSTDCPP depends on BR2_TOOLCHAIN_HAS_THREADS + depends on !BR2_TOOLCHAIN_USES_UCLIBC
Please add a comment explaining this dependency. Something like:
depends on !BR2_TOOLCHAIN_USES_UCLIBC # getspnam()
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 -PATCH v2 1/1 sconeserver: Can't be built with uClibc.
In reply to Sonic ZhangQuoted 6 lines
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
"Sonic" == Sonic Zhang <[email protected]> writes:
From: Sonic Zhang <[email protected]>
General shadow password file API such as getspnam is not supported in uClibc.
Ehh, they are?
./output/host/usr/bin/arm-linux-nm -D \
output/target/lib/libuClibc-0.9.33.2.so | grep getspnam0002a6c0 T getspnam0002a6f0 T getspnam_r
They do require you to enable UCLIBC_HAS_SHADOW, but that option defaults to y and our default config has it enabled.
Signature · 1 line
Bye, Peter Korsgaard
PATCH v2 1/1 sconeserver: Can't be built with uClibc.
Quoted 9 lines · Peter Korsgaard
Quoted 6 lines
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
"Sonic" == Sonic Zhang <[email protected]> writes:
From: Sonic Zhang <[email protected]>
General shadow password file API such as getspnam is not supported in uClibc.
Ehh, they are?
Quoted 8 lines
./output/host/usr/bin/arm-linux-nm -D \
output/target/lib/libuClibc-0.9.33.2.so | grep getspnam0002a6c0T getspnam0002a6f0Tgetspnam_rThey do require you to enable
UCLIBC_HAS_SHADOW, but that option defaults to y and our default config has it enabled.
In the case the UCLIBC_HAS_SHADOW is not supported in the GNU toolchain release for some architecture such as Blackfin, how should the building failure be dealt with?
Regards,
Sonic
PATCH v2 1/1 sconeserver: Can't be built with uClibc.
Quoted 12 lines
Quoted 12 lines
Quoted 4 lines
Quoted 1 line
Quoted 1 line
"Sonic" == Sonic Zhang <[email protected]> writes:
General shadow password file API such as getspnam is not supported in uClibc.
Ehh, they are?
./output/host/usr/bin/arm-linux-nm -D \
output/target/lib/libuClibc-0.9.33.2.so | grep getspnam0002a6c0T getspnam0002a6f0Tgetspnam_r
Quoted 7 lines
Quoted 3 lines
They do require you to enable
UCLIBC_HAS_SHADOW, but that option defaults to y and our default config has it enabled.In the case the
UCLIBC_HAS_SHADOWis not supported in the GNU toolchain release for some architecture such as Blackfin, how should the building failure be dealt with?
For external toolchains you mean? We can do a few things:
- Mention the dependency in the Config.in help text
- If it's a preconfigured / well known toolchain in buildroot we can:
- Disable the combination in the autobuilders
- Explicitly make the package depend on !<specific-toolchain>
Signature · 1 line
Bye, Peter Korsgaard