From: Enrico Scholz <enrico.scholz@sigma-chemnitz.de>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH] gcc: enable zstd compression of LTO bytecode
Date: Fri, 04 Feb 2022 20:00:47 +0100 [thread overview]
Message-ID: <ly5ypujw2o.fsf@ensc-virt.intern.sigma-chemnitz.de> (raw)
In-Reply-To: <daba354376a2183ff81594c226a5a4bae1cbe96e.camel@linuxfoundation.org> (Richard Purdie's message of "Thu, 03 Feb 2022 21:59:16 +0000")
Richard Purdie <richard.purdie@linuxfoundation.org> writes:
>> | lto1: internal compiler error: original not compressed with zstd
>>
>> DEPENDS =+ "mpfr gmp libmpc zlib flex-native"
>> -NATIVEDEPS = "mpfr-native gmp-native libmpc-native zlib-native flex-native"
>> +NATIVEDEPS = "mpfr-native gmp-native libmpc-native zlib-native flex-native zstd-native"
>>
>> LICENSE = "GPL-3.0-with-GCC-exception & GPLv3"
>>
>
> Should we be passing some flag to gcc explicitly to configure this
> deterministicly?
Both '--with-zstd' and '--without-zstd' make it deterministic (require
zstd.h and abort when non-existing resp. ignore it when existing).
Perhaps '--without-zstd' should be added in the hardknott and honister
branches to prevent pollution by host environment.
Enrico
next prev parent reply other threads:[~2022-02-04 19:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-03 17:26 [PATCH] gcc: enable zstd compression of LTO bytecode Enrico Scholz
2022-02-03 19:23 ` [OE-core] " Khem Raj
2022-02-03 21:40 ` Enrico Scholz
2022-02-03 21:48 ` Khem Raj
2022-02-03 21:59 ` Richard Purdie
2022-02-03 22:11 ` Khem Raj
2022-02-03 22:21 ` Richard Purdie
2022-02-04 19:00 ` Enrico Scholz [this message]
2022-02-04 21:00 ` Khem Raj
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ly5ypujw2o.fsf@ensc-virt.intern.sigma-chemnitz.de \
--to=enrico.scholz@sigma-chemnitz.de \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox