I think due to not jet compiled gcc, configure script fail with: checking whether gcc implicitly enables -fstack-protector... arm-hardfloat-linux-gnueabi-nm: conftest.o: File format is ambiguous arm-hardfloat-linux-gnueabi-nm: Matching formats: elf64-little elf64-x86-64-nacl elf64-x86-64-sol2 elf64-x86-64 erleare in the configure output: checking for arm-hardfloat-linux-gnueabi-gcc... gcc Reproducible: Always
Created attachment 329712 [details] cross-arm-hardfloat-linux-gnueabi-glibc-headers.log.xz
Created attachment 329714 [details] cross-arm-hardfloat-linux-gnueabi-info.log
Created attachment 329716 [details] glibc-config.logs.tar.xz
Got compiled as following: crossdev -t arm-hardfloat-linux-gnueabi -s1 --without-headers and with this patch: diff --git a/sys-libs/glibc/files/eblits/src_compile.eblit b/sys-libs/glibc/files/eblits/src_compile.eblit index cb4cc0b..1bb3c96 100644 --- a/sys-libs/glibc/files/eblits/src_compile.eblit +++ b/sys-libs/glibc/files/eblits/src_compile.eblit @@ -176,7 +176,6 @@ toolchain-glibc_headers_compile() { # so forcing CC/CFLAGS is sane. unless you dont have `gcc`. then i # dont care :p. echo "${S}"/configure ${myconf} - CC=gcc \ CFLAGS="-O1 -pipe" \ CPPFLAGS="-U_FORTIFY_SOURCE" \ LDFLAGS="" \ It seems, that this workaround don't work anymore.
Created attachment 329758 [details, diff] eblit and ebuild patch This pacth do the trick for me. 1. "CC=gcc"-trick don't needed anymore, if you build only header 2. don't ignore binutils and gcc dependencies on crosscompile_opts_headers-only 3. systemtap useflag don't work for arm jet
Comment on attachment 329758 [details, diff] eblit and ebuild patch this is pretty much all wrong
should be all set now in the tree; thanks for the report! Commit message: Disable fortify/ssp compiler checks when build glibc headers http://sources.gentoo.org/sys-libs/glibc/files/eblits/src_compile.eblit?r1=1.28&r2=1.29
Please remove systemtap use flag for arm platform, it won't build with systemtap use flag.
Patch don't work. Still same error.
Created attachment 329894 [details] configure.log Configure log with the error.
Sorry, didn't had that patch. Now all working.