[Bug ld/28859] New: Assertion failed while building glibc on raspbian bookworm.

[plugwash at p10link dot net]

https://sourceware.org/bugzilla/show_bug.cgi?id=28859

            Bug ID: 28859
           Summary: Assertion failed while building glibc on raspbian
                    bookworm.
           Product: binutils
           Version: 2.38
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: ld
          Assignee: unassigned at sourceware dot org
          Reporter: plugwash at p10link dot net
  Target Milestone: ---

Created attachment 13955
  --> https://sourceware.org/bugzilla/attachment.cgi?id=13955&action=edit
files needed to trigger assert.

I maintain raspbian, unfortunately my attemts to update glibc in raspbian
bookworm are failing with an assertion failre.

The bintutils package in Raspbian bookworm is based on that from Debian
bookworm and is currently at 2.37.90.20220123-2+rpi1

arm-linux-gnueabihf-gcc-10   -shared -static-libgcc 
-Wl,-dynamic-linker=/lib/ld-linux-armhf.so.3 -Wl,-z,defs
-B/glibc/build-tree/armhf-libc/csu/  -Wl,-z,combreloc -Wl,-z,relro
-Wl,--hash-style=both  -L/glibc/build-tree/armhf-libc
-L/glibc/build-tree/armhf-libc/math -L/glibc/build-tree/armhf-libc/elf
-L/glibc/build-tree/armhf-libc/dlfcn -L/glibc/build-tree/armhf-libc/nss
-L/glibc/build-tree/armhf-libc/nis -L/glibc/build-tree/armhf-libc/rt
-L/glibc/build-tree/armhf-libc/resolv -L/glibc/build-tree/armhf-libc/mathvec
-L/glibc/build-tree/armhf-libc/support -L/glibc/build-tree/armhf-libc/nptl
-Wl,-rpath-link=/glibc/build-tree/armhf-libc:/glibc/build-tree/armhf-libc/math:/glibc/build-tree/armhf-libc/elf:/glibc/build-tree/armhf-libc/dlfcn:/glibc/build-tree/armhf-libc/nss:/glibc/build-tree/armhf-libc/nis:/glibc/build-tree/armhf-libc/rt:/glibc/build-tree/armhf-libc/resolv:/glibc/build-tree/armhf-libc/mathvec:/glibc/build-tree/armhf-libc/support:/glibc/build-tree/armhf-libc/nptl
-o /glibc/build-tree/armhf-libc/elf/sotruss-lib.so 
/glibc/build-tree/armhf-libc/csu/abi-note.o -Wl,--as-needed
/glibc/build-tree/armhf-libc/elf/sotruss-lib.os  -Wl,--no-as-needed
-Wl,--start-group /glibc/build-tree/armhf-libc/libc.so
/glibc/build-tree/armhf-libc/libc_nonshared.a -Wl,--as-needed
/glibc/build-tree/armhf-libc/elf/ld.so -Wl,--no-as-needed -Wl,--end-group

collect2: error: ld returned 1 exit status

I checked that the line where the assert triggered was the same in our binutils
tree as it is in current git head.

14800               /* If the output has no requirement about FP hardware,
14801                  follow the requirement of the input.  */
14802               if (out_attr[i].i == 0)
14803                 {
14804                   /* This assert is still reasonable, we shouldn't
14805                      produce the suspicious build attribute
14806                      combination (See below for in_attr).  */
14807                   BFD_ASSERT (out_attr[Tag_ABI_HardFP_use].i == 0);
14808                   out_attr[i].i = in_attr[i].i;
14809                   out_attr[Tag_ABI_HardFP_use].i
14810                     = in_attr[Tag_ABI_HardFP_use].i;
14811                   break;
14812                 }

I was able to reduce the command needed to trigger the assert to /usr/bin/ld
-shared /glibc/build-tree/armhf-libc/csu/crti.o
/usr/lib/gcc/arm-linux-gnueabihf/10/crtendS.o

-- 
You are receiving this mail because:
You are on the CC list for the bug.