From: Ralph Siemsen Date: Fri, 15 Apr 2022 00:12:28 +0000 (-1000) Subject: apt: add -fno-strict-aliasing to CXXFLAGS to fix SHA256 bug X-Git-Tag: yocto-3.1.16~12 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=dc61dfd7791976c70c93e0d253a8fdbd40d27f3b;p=thirdparty%2Fopenembedded%2Fopenembedded-core.git apt: add -fno-strict-aliasing to CXXFLAGS to fix SHA256 bug Recently we've begun seeing issues with apt SHA256 generation/checking on some distros (fedora 35, alma 8). The version of apt in dunfell uses its own SHA256 code, not a standard library. Investigation reveals that the issue is related to -fstrict-aliasing enabled by -O2 optimization, so turn it off with -fno-strict-aliasing Signed-off-by: Ralph Siemsen Signed-off-by: Steve Sakoman --- diff --git a/meta/recipes-devtools/apt/apt.inc b/meta/recipes-devtools/apt/apt.inc index ba827848a74..251795eeca3 100644 --- a/meta/recipes-devtools/apt/apt.inc +++ b/meta/recipes-devtools/apt/apt.inc @@ -37,5 +37,9 @@ do_configure_prepend() { rm -rf ${S}/buildlib/config.guess } +# there are code generation issues with some compilers in the SHA256 implementation +# turn off strict-aliasing to avoid these issues +CXXFLAGS:append = " -fno-strict-aliasing" + USERADD_PACKAGES = "${PN}" USERADD_PARAM_${PN} = "--system --no-create-home --home-dir /nonexistent --shell /bin/false --user-group _apt"