Historically, the MD5 checksums in our LFS files serve as a protection
against broken downloads, or accidentally corrupted source files.
While the sources are nowadays downloaded via HTTPS, it make sense to
beef up integrity protection for them, since transparently intercepting
TLS is believed to be feasible for more powerful actors, and the state
of the public PKI ecosystem is clearly not helping.
Therefore, this patch switches from MD5 to BLAKE2, updating all LFS
files as well as make.sh to deal with this checksum algorithm. BLAKE2 is
notably faster (and more secure) than SHA2, so the performance penalty
introduced by this patch is negligible, if noticeable at all.
In preparation of this patch, the toolchain files currently used have
been supplied with BLAKE2 checksums as well on
https://source.ipfire.org/.
Cc: Michael Tremer <michael.tremer@ipfire.org>
Signed-off-by: Peter Müller <peter.mueller@ipfire.org>
Acked-by: Michael Tremer <michael.tremeripfire.org>
This patch removes support for i586 according to the decision being
taken over a year ago.
It removes the architecture from the build system and removes all
required hacks and other quirks that have been necessary before.
There is no need to ship any changed files to the remaining
architectures as the removed code branches have not been used.
Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
we have no supported armv5tel board left so we can switch to the higher
arch. This now can use the vpu (still in softfp calling convention to
not break existing installations.)
this fix many compile problems, also boost is now working again.
Signed-off-by: Arne Fitzenreiter <arne_f@ipfire.org>
"g++" -fvisibility-inlines-hidden -fPIC -O3 -finline-functions -Wno-inline -Wall -fvisibility=hidden -O2 -pipe -Wall -fexceptions -fPIC -march=armv5te -mfloat-abi=soft -fomit-frame-pointer -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -fstack-protector-strong -O3 -fno-strict-aliasing -O2 -pipe -Wall -fexceptions -fPIC -march=armv5te -mfloat-abi=soft -fomit-frame-pointer -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -fstack-protector-strong -O3 -fno-strict-aliasing -DBOOST_ALL_NO_LIB=1 -DBOOST_REGEX_DYN_LINK=1 -DNDEBUG -I"." -c -o "serial/boost/bin.v2/libs/regex/build/gcc-10.2.0/release/pch-off/visibility-hidden/wide_posix_api.o" "libs/regex/build/../src/wide_posix_api.cpp"
In file included from ./boost/regex/v5/perl_matcher_non_recursive.hpp:23,
from ./boost/regex/v5/perl_matcher.hpp:572,
from ./boost/regex/v5/regex.hpp:45,
from ./boost/regex.hpp:34,
from libs/regex/build/../src/wide_posix_api.cpp:25:
./boost/regex/v5/mem_block_cache.hpp:91:11: error: 'static_mutex' in namespace 'boost' does not name a type
91 | boost::static_mutex mut;
| ^~~~~~~~~~~~
./boost/regex/v5/mem_block_cache.hpp: In member function 'void* boost::re_detail_500::mem_block_cache::get()':
./boost/regex/v5/mem_block_cache.hpp:106:37: error: 'mut' was not declared in this scope; did you mean 'put'?
106 | std::lock_guard<std::mutex> g(mut);
| ^~~
| put
./boost/regex/v5/mem_block_cache.hpp: In member function 'void boost::re_detail_500::mem_block_cache::put(void*)':
./boost/regex/v5/mem_block_cache.hpp:120:37: error: 'mut' was not declared in this scope; did you mean 'put'?
120 | std::lock_guard<std::mutex> g(mut);
| ^~~
| put
./boost/regex/v5/mem_block_cache.hpp: In static member function 'static boost::re_detail_500::mem_block_cache& boost::re_detail_500::mem_block_cache::instance()':
./boost/regex/v5/mem_block_cache.hpp:137:52: error: 'BOOST_STATIC_MUTEX_INIT' was not declared in this scope; did you mean 'BOOST_STATIC_CONSTANT'?
137 | static mem_block_cache block_cache = { 0, 0, BOOST_STATIC_MUTEX_INIT, };
| ^~~~~~~~~~~~~~~~~~~~~~~
| BOOST_STATIC_CONSTANT
./boost/regex/v5/mem_block_cache.hpp:137:77: error: too many initializers for 'boost::re_detail_500::mem_block_cache'
137 | static mem_block_cache block_cache = { 0, 0, BOOST_STATIC_MUTEX_INIT, };
| ^
...failed updating 2 targets...
make: *** [boost:102: /usr/src/log/boost_1_76_0] Error 1
Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
- Update from 1_71_0 to 1_76_0
- Update rootfile for x86_64 and copy for other architectures by replacing
x64 with x32 for i586, a32 for armv5tel and a64 for aarch64
- Make build use python3
- add link=shared to build to only have shared libraries created, except for
libboost_exception and libboost_test_exec_monitor which are only
created as static versions
- Changelog
Fixes
algorithm::reduce with crop now does not remove the counts in flow
bins anymore if the selected range actually overlaps with the flow
bins, making the treatment of flow bins consistent with inner bins
accumulators::mean and accumulators::weighted_mean now compute the
correct variance when operator+= was called, for example, when
histograms with accumulators are added; this was wrong before
leading to too small variances
detection of weight support in user-defined accumulators was broken
at compile-time if accumulator used operator+= instead of
operator(); tests only accidentally passed for builtin weighted_sum
Signed-off-by: Adolf Belka <adolf.belka@ipfire.org>
Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
I did not update to the current version 1.74.0 because another package
I want to submit do not build with the current version.
I do not think this is a big show stopper because other distributions
are not on the latest version either.
The removed switch do not seem to be availavle in this version anymore.
Signed-off-by: Jonatan Schlag <jonatan.schlag@ipfire.org>
Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
This will now adjust MAKETUNING to not launch more processes
than MAX_PARALLELISM. Handy to limit builds that use a lot of memory.
Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
Most of these files still used old dates and/or domain names for contact
mail addresses. This is now replaced by an up-to-date copyright line.
Just some housekeeping... :-)
Signed-off-by: Peter Müller <peter.mueller@link38.eu>
Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
