5155a8bd1c
In commit 87492d244a ("aiccu: disable
for uClibc 0.9.31/0.9.32"), we made sure it was not possible to select
aiccu with uClibc 0.9.31 and 0.9.32, because they lack dn_skipname().
However, we still have the problem that external AVR32 toolchains can
select aiccu, which causes build failures. Therefore, we also disallow
aiccu on AVR32 altogether. We keep the 0.9.31/0.9.32 exclusions,
because if they are used on other architectures, it would also fail
due to the lack of dn_skipname().
Fixes:
http://autobuild.buildroot.org/results/a24/a2490d434152625d9208615d83f4c5d6daea79d0/
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
32 lines
1.1 KiB
Plaintext
32 lines
1.1 KiB
Plaintext
config BR2_PACKAGE_AICCU
|
|
bool "aiccu"
|
|
depends on BR2_INET_IPV6
|
|
depends on BR2_USE_WCHAR
|
|
depends on BR2_TOOLCHAIN_HAS_THREADS
|
|
depends on BR2_USE_MMU # fork()
|
|
# Uses dn_skipname(), only available since 0.9.33
|
|
depends on !BR2_UCLIBC_VERSION_0_9_31 && \
|
|
!BR2_UCLIBC_VERSION_0_9_32
|
|
# AVR32 only has uClibc 0.9.31, so there's no way it can build
|
|
# due to the lack of dn_skipname(), even with external
|
|
# toolchains.
|
|
depends on !BR2_avr32
|
|
select BR2_PACKAGE_GNUTLS
|
|
help
|
|
SixXS Automatic IPv6 Connectivity Client Utility
|
|
|
|
AICCU (Automatic IPv6 Connectivity Client Utility) makes it
|
|
easy for users to get IPv6 connectivity. After having
|
|
requested an account, tunnel and optionally a subnet, AICCU
|
|
can be used to automatically configure the tunnel. AICCU
|
|
supports TIC (Tunnel Information & Control protocol), which it
|
|
uses for retrieving the tunnel configuration information,
|
|
AYIYA, which allows tunnels to be created even behind
|
|
firewalls and NAT's.
|
|
|
|
http://www.sixxs.net/tools/aiccu/
|
|
|
|
comment "aiccu needs a toolchain w/ IPv6, wchar, threads"
|
|
depends on BR2_USE_MMU
|
|
depends on !(BR2_INET_IPV6 && BR2_USE_WCHAR && BR2_TOOLCHAIN_HAS_THREADS)
|