bug-binutils
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug ld/23194] Building glibc 2.27 on 32-bit Intel with binutils 2.30 se


From: hjl.tools at gmail dot com
Subject: [Bug ld/23194] Building glibc 2.27 on 32-bit Intel with binutils 2.30 segfaults in elf subdir
Date: Fri, 18 May 2018 18:18:50 +0000

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

--- Comment #7 from H.J. Lu <hjl.tools at gmail dot com> ---
(In reply to Andreas Baumann from comment #6)
> (In reply to H.J. Lu from comment #5)
> > I can build glibc 2.27 on i686.  Please provide ALL linker inputs
> > so that I can reproduce it.
> 
> Hope this helps:
> 
> gcc   -nostdlib -nostartfiles -shared -o
> /root/glibc/src/glibc-build/elf/ld.so.new             \
>           -Wl,-z,combreloc -Wl,-z,relro -Wl,--hash-style=both -Wl,-z,defs
> -Wl,-z,now   \
>           /root/glibc/src/glibc-build/elf/librtld.os
> -Wl,--version-script=/root/glibc/src/glibc-build/ld.map           \
>           -Wl,-soname=ld-linux.so.2                     \
>           -Wl,-defsym=_begin=0
> 
> segfaults, but ommiting '-shared' works:
> 
> gcc   -nostdlib -nostartfiles -o /root/glibc/src/glibc-build/elf/ld.so.new  
> \
>           -Wl,-z,combreloc -Wl,-z,relro -Wl,--hash-style=both -Wl,-z,defs
> -Wl,-z,now   \
>           /root/glibc/src/glibc-build/elf/librtld.os
> -Wl,--version-script=/root/glibc/src/glibc-build/ld.map           \
>           -Wl,-soname=ld-linux.so.2                     \
>           -Wl,-defsym=_begin=0

It doesn't help at all.  Please add -v to gcc and show me the output of

# gcc -v  -nostdlib -nostartfiles -shared -o
/root/glibc/src/glibc-build/elf/ld.so.new             \
          -Wl,-z,combreloc -Wl,-z,relro -Wl,--hash-style=both -Wl,-z,defs
-Wl,-z,now   \
          /root/glibc/src/glibc-build/elf/librtld.os
-Wl,--version-script=/root/glibc/src/glibc-build/ld.map           \
          -Wl,-soname=ld-linux.so.2                     \
          -Wl,-defsym=_begin=0

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


reply via email to

[Prev in Thread] Current Thread [Next in Thread]