-mabi=elfv2 is default on ppc64le in gcc/glibc toolchain for all powerpc64le-*-linux-gnu CHOSTS, so we don't need to pass it.
forcing -mabi=elfv2 on ppc64(be) is quite risky, as it's not standard configuration and not officialy supported by glibc at all. according to glibc upstream it should be a separate ABI port. Also many apps/tools assume elfv1 on big-endian, and while fixes are being upstreamed, we've observed breakage in: openssl[asm], nodejs, ffmpeg and others. If we want to ship elfv2 ppc64be stage, we should define it as separate subarch and strictly put it in experimental. to my knowledge those subarch definitions are not used by releng yet, so we will not break anything. Signed-off-by: Georgy Yakovlev <gyakov...@gentoo.org> --- arch/ppc.toml | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/arch/ppc.toml b/arch/ppc.toml index 870c7647..6f74789d 100644 --- a/arch/ppc.toml +++ b/arch/ppc.toml @@ -23,22 +23,22 @@ CHOST = "powerpc64-unknown-linux-gnu" USE = [ "altivec", "ibm",] [ppc64.power7] -COMMON_FLAGS = "-O2 -pipe -mcpu=power7 -mtune=power7 -mabi=elfv2" +COMMON_FLAGS = "-O2 -pipe -mcpu=power7 -mtune=power7" CHOST = "powerpc64-unknown-linux-gnu" USE = [ "altivec", "ibm",] [ppc64.power7le] -COMMON_FLAGS = "-O2 -pipe -mcpu=power7 -mtune=power7 -mabi=elfv2" +COMMON_FLAGS = "-O2 -pipe -mcpu=power7 -mtune=power7" CHOST = "powerpc64le-unknown-linux-gnu" USE = [ "altivec", "ibm",] [ppc64.power8] -COMMON_FLAGS = "-O2 -pipe -mcpu=power8 -mtune=power8 -mabi=elfv2" +COMMON_FLAGS = "-O2 -pipe -mcpu=power8 -mtune=power8" CHOST = "powerpc64-unknown-linux-gnu" USE = [ "altivec", "ibm",] [ppc64.power8le] -COMMON_FLAGS = "-O2 -pipe -mcpu=power8 -mtune=power8 -mabi=elfv2" +COMMON_FLAGS = "-O2 -pipe -mcpu=power8 -mtune=power8" CHOST = "powerpc64le-unknown-linux-gnu" USE = [ "altivec", "ibm",] -- 2.29.0
