This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug libc/22144] New: libc.so.6: ELF file OS ABI invalid
- From: "bastl at eclipso dot de" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sourceware dot org
- Date: Sat, 16 Sep 2017 22:52:28 +0000
- Subject: [Bug libc/22144] New: libc.so.6: ELF file OS ABI invalid
- Auto-submitted: auto-generated
https://sourceware.org/bugzilla/show_bug.cgi?id=22144
Bug ID: 22144
Summary: libc.so.6: ELF file OS ABI invalid
Product: glibc
Version: 2.26
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: libc
Assignee: unassigned at sourceware dot org
Reporter: bastl at eclipso dot de
CC: drepper.fsp at gmail dot com
Target Milestone: ---
I compiled ftp://ftp.gnu.org/gnu/glibc/glibc-2.26.tar.xz
with:
-linux-4.9.38
-gcc (GCC) 6.3.0
-GNU ld (GNU Binutils) 2.28
-GNU Awk 4.1.4
-perl 5, version 24, subversion 0 (v5.24.0)
-GNU Make 4.2.1
-libtool (GNU libtool) 2.4.6
for:
-i686-pc-linux-gnu
If I want to use the new glibc I get this error, too:
chroot /mnt/hdb5/SYS-2/
Inconsistency detected by ld.so: get-dynamic-info.h: 143: elf_get_dynamic_info:
Assertion `info[DT_RPATH] == NULL' failed!
bash-4.4# readelf -h ./ld-2.26.so
ELF Header:
Magic: 7f 45 4c 46 01 01 01 00 00 00 00 00 00 00 00 00
Class: ELF32
Data: 2's complement, little endian
Version: 1 (current)
OS/ABI: UNIX - System V
ABI Version: 0
Type: DYN (Shared object file)
Machine: Intel 80386
Version: 0x1
Entry point address: 0xb50
Start of program headers: 52 (bytes into file)
Start of section headers: 1175960 (bytes into file)
Flags: 0x0
Size of this header: 52 (bytes)
Size of program headers: 32 (bytes)
Number of program headers: 6
Size of section headers: 40 (bytes)
Number of section headers: 32
Section header string table index: 29
I guess that 80% of all plans compiling glibc from source is to upgrade from a
8-12 years old system to a newest one. So this should be the default initial
position for developing glibc, binutils, ...
--
You are receiving this mail because:
You are on the CC list for the bug.