Hi Alex, > This fails to build glibc, but doesn't exactly give much info: > > * Log: /var/log/portage/cross-mipsr5900el-unknown-linux-gnu-binutils.log > * Emerging cross-binutils ... [ > ok ] > * Log: > /var/log/portage/cross-mipsr5900el-unknown-linux-gnu-linux-headers-quick.log > * Emerging cross-linux-headers-quick ... [ > ok ] > * Log: > /var/log/portage/cross-mipsr5900el-unknown-linux-gnu-glibc-headers.log > * Emerging cross-glibc-headers ... > > * error: glibc failed :( > * > * If you file a bug, please attach the following logfiles: > * /var/log/portage/cross-mipsr5900el-unknown-linux-gnu-info.log > * /var/log/portage/cross-mipsr5900el-unknown-linux-gnu-glibc-headers.log.xz > * > /var/tmp/portage/cross-mipsr5900el-unknown-linux-gnu/glibc*/temp/glibc-config.logs.tar.xz > The command '/bin/sh -c crossdev -s3 -t mipsr5900el-unknown-linux-gnu > --binutils ">=2.30" --gcc ">=7.2.0"' returned a non-zero code: 1
I would recommend using GCC 8.2.0, by omitting the --binutils and --gcc options to crossdev, unless you would like to debug this particular combination of GCC and Glibc (which I can confirm seems broke). Updated and much simplified R5900 patches are available in my previous email: http://lists.nongnu.org/archive/html/qemu-devel/2018-11/msg03649.html Hopefully soon, with upcoming GCC and Gblic releases, no R5900 patches are needed at all. Also, a new -mfix-r5900 option has been proposed to both GAS and GCC: http://www.sourceware.org/ml/binutils/2018-10/msg00301.html https://gcc.gnu.org/ml/gcc-patches/2018-11/msg00773.html With that option one can compile e.g. MIPS II or MIPS III that also work with the R5900. The R3900 and the R5900 could for example run the same programs then, and I do hope that Philippe will be able to merge his R3900 series eventually. Fredrik
