481310c9ad
The efivar internal build system uses flags such as -std=gnu11 , -Wmaybe-uninitialized , -flto which are available in gcc >= 4.7 only. These flags are passed both to target build and to build a host tool. For the host part, this has been worked around by overriding 'gcc_flags', but doing that for the target would remove all flags that upstream intended for the target build. Buildroot doesn't support building gcc 4.6 in its own toolchain anymore but it's possible to use an external toolchain with gcc 4.6 which would be unable to build this package. This patch adds a limitation on toolchains with target gcc >= 4.7 to make sure that the flags are available in the chosen toolchain. Signed-off-by: Erico Nunes <nunes.erico@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
18 lines
619 B
Plaintext
18 lines
619 B
Plaintext
config BR2_PACKAGE_EFIVAR
|
|
bool "efivar"
|
|
depends on BR2_TOOLCHAIN_HEADERS_AT_LEAST_3_12 # linux/nvme.h
|
|
# doesn't build with uclibc due to lack of uchar.h
|
|
# doesn't build with musl due to lack of __bswap_constant_16
|
|
depends on BR2_TOOLCHAIN_USES_GLIBC
|
|
depends on BR2_TOOLCHAIN_GCC_AT_LEAST_4_7
|
|
select BR2_PACKAGE_POPT
|
|
help
|
|
Tools and libraries to manipulate EFI variables
|
|
|
|
https://github.com/rhinstaller/efivar
|
|
|
|
comment "efivar requires a glibc toolchain w/ headers >= 3.12, gcc >= 4.7"
|
|
depends on !BR2_TOOLCHAIN_HEADERS_AT_LEAST_3_12 || \
|
|
!BR2_TOOLCHAIN_USES_GLIBC || \
|
|
!BR2_TOOLCHAIN_GCC_AT_LEAST_4_7
|