[Buildroot] [PATCH] schifra: mark as broken
Thomas Petazzoni
thomas.petazzoni at free-electrons.com
Sun Nov 9 10:53:30 UTC 2014
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 at free-electrons.com>
---
package/schifra/Config.in | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/package/schifra/Config.in b/package/schifra/Config.in
index 486f92d..a3f699a 100644
--- a/package/schifra/Config.in
+++ b/package/schifra/Config.in
@@ -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
--
2.0.0
More information about the buildroot
mailing list