gcc: Compile without ZSTD

GCC can use ZSTD to compress debugging/LTO information in binary
objects. However, on riscv64, compiling zstd requires libatomic which is
not available at this point.

In order to make the build work, we explicitely disable ZSTD in GCC and
build ZSTD after libatomic is available.

Although ZSTD offers great compression, we won't have any disadvantages
through this change since we do not ship any debugging information and
at this point in time to not use LTO.

Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
This commit is contained in:
Michael Tremer
2022-02-22 12:51:25 +00:00
committed by Peter Müller
parent d79715dbf9
commit 0b6ba4a0ca
2 changed files with 3 additions and 2 deletions

View File

@@ -182,7 +182,8 @@ EXTRA_CONFIG += \
--disable-multilib \
--with-bugurl=https://bugzilla.ipfire.org \
--disable-libunwind-exceptions \
--enable-gnu-unique-object
--enable-gnu-unique-object \
--without-zstd
export XCFLAGS = $(CFLAGS)
export TCFLAGS = $(CFLAGS)

View File

@@ -1079,7 +1079,6 @@ buildbase() {
lfsmake2 tzdata
lfsmake2 cleanup-toolchain
lfsmake2 zlib
lfsmake2 zstd
lfsmake2 autoconf
lfsmake2 automake
lfsmake2 libtool
@@ -1090,6 +1089,7 @@ buildbase() {
lfsmake2 libxcrypt
lfsmake2 file
lfsmake2 gcc
lfsmake2 zstd
lfsmake2 sed
lfsmake2 berkeley
lfsmake2 coreutils