Created attachment 878815 [details] cross-powerpc-unknown-linux-gnu-info.log crossdev -S -t ppc * crossdev version: 20230923 * Host Portage ARCH: amd64 * Host Portage System: x86_64-pc-linux-gnu (i686-pc-linux-gnu x86_64-pc-linux-gnu) * Target Portage ARCH: ppc * Target System: powerpc-unknown-linux-gnu * Stage: 4 (C/C++ compiler) * USE=multilib: no * Target ABIs: default * binutils: binutils-[stable] * gcc: gcc-[stable] * headers: linux-headers-[stable] * libc: glibc-[stable] * CROSSDEV_OVERLAY: /var/db/repos/crossdev * PORT_LOGDIR: /var/log/portage * PORTAGE_CONFIGROOT: / * Portage flags: _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - * leaving metadata/layout.conf alone in /var/db/repos/crossdev _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - * Log: /var/log/portage/cross-powerpc-unknown-linux-gnu-binutils.log * Emerging cross-binutils ... [ ok ] * Log: /var/log/portage/cross-powerpc-unknown-linux-gnu-gcc-stage1.log * Emerging cross-gcc-stage1 ... [ ok ] * Log: /var/log/portage/cross-powerpc-unknown-linux-gnu-linux-headers.log * Emerging cross-linux-headers ... [ ok ] * Log: /var/log/portage/cross-powerpc-unknown-linux-gnu-glibc.log * Emerging cross-glibc ... * error: glibc failed :( * * If you file a bug, please attach the following logfiles: * /var/log/portage/cross-powerpc-unknown-linux-gnu-info.log * /var/log/portage/cross-powerpc-unknown-linux-gnu-glibc.log.xz * /var/tmp/portage/cross-powerpc-unknown-linux-gnu/glibc*/temp/glibc-config.logs.tar.xz [...] checking if gcc -pipe -O2 -fcf-protection=none -fuse-ld=bfd -Wl,-O1 -Wl,--as-needed accepts -fn o-tree-loop-distribute-patterns with __attribute__ ((__optimize__))... yes checking for libgd... no checking for _FORTIFY_SOURCE predefine... yes checking whether the assembler requires one version per symbol... no checking for __builtin_trap with no external dependencies... yes checking whether the C++ compiler supports thread_local... no running configure fragment for sysdeps/unix/sysv/linux/powerpc/powerpc32 running configure fragment for sysdeps/unix/sysv/linux/powerpc checking whether gcc -pipe -O2 -fcf-protection=none -fuse-ld=bfd -Wl,-O1 -Wl,--as-needed -pipe -O2 -fcf-protection=none -mlong-double-128 uses IBM extended format... no checking whether gcc -pipe -O2 -fcf-protection=none -fuse-ld=bfd -Wl,-O1 -Wl,--as-needed -pipe -O2 -fcf-protection=none supports -mabi=ibmlongdouble... no configure: error: this configuration requires -mlong-double-128 IBM extended format support * ERROR: cross-powerpc-unknown-linux-gnu/glibc-2.37-r7::crossdev failed (configure phase): * failed to configure glibc
Created attachment 878816 [details] cross-powerpc-unknown-linux-gnu-glibc.log.xz
Created attachment 878817 [details] glibc-config.logs.tar.xz
Created attachment 878818 [details] emerge --info
This part looks very suspicious. > configure:2326: checking for powerpc-unknown-linux-gnu-gcc > configure:2353: result: gcc -pipe -O2 -fcf-protection=none -fuse-ld=bfd -Wl,-O1 -Wl,--as-needed I get the same if I manually set CC=gcc.
(In reply to James Le Cuirot from comment #4) > This part looks very suspicious. > > I get the same if I manually set CC=gcc. Ah yes, on this system I actually had forced CC=gcc, 'O2' and ld=bfd for crossdev packages via package.env as make.conf settings are 'Os' ld=mold. You are correct that cross-powerpc-unknown-linux-gnu-glibc builds ok by simply not forcing gcc. Forcing 'O2' and ld=bfd via package.env works ok though. My bad. Sorry for the noise.
