schifra: mark as broken
There are many build failures caused by schifra, due to upstream changing the tarball without doing new releases. Since has been an on-going problem for some time, and is now the #1 issue in the autobuilders. So let's mark this package broken, until someone cares enough to fix it, or until we remove it. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
This commit is contained in:
parent
74128856f4
commit
54f3f58b2b
@ -1,6 +1,10 @@
|
||||
config BR2_PACKAGE_SCHIFRA
|
||||
bool "schifra"
|
||||
depends on BR2_INSTALL_LIBSTDCPP
|
||||
# Upstream keep changing the tarball without doing new
|
||||
# releases. This is not acceptable for Buildroot, as
|
||||
# reproducible builds are very important.
|
||||
depends on BR2_BROKEN
|
||||
help
|
||||
Schifra is a very robust, highly optimized and extremely configurable
|
||||
Reed-Solomon error correcting code library for both software and IP
|
||||
@ -18,4 +22,5 @@ config BR2_PACKAGE_SCHIFRA_EXAMPLES
|
||||
endif
|
||||
|
||||
comment "schifra needs a toolchain w/ C++"
|
||||
depends on BR2_BROKEN
|
||||
depends on !BR2_INSTALL_LIBSTDCPP
|
||||
|
Loading…
Reference in New Issue
Block a user