在Gentoo主机上出现-uDN世界失败，sys-libs/glibc-2.20-r2不链接。

Question

我们有许多传统的基于Gentoo的机器，并且正在试图升级它们。这些主机中至少有三台失败，出现了最新的glibc错误：

x86_64-pc-linux-gnu-gcc -m32 -Wl,-O1 -Wl,--as-needed -Wl,-O1 -Wl,--as-needed  -shared -static-libgcc -Wl,-O1  -Wl,-z,defs -Wl,-dynamic-linker=/lib32/ld-linux.so.2  -B/v
ar/tmp/portage/sys-libs/glibc-2.20-r2/work/build-x86-x86_64-pc-linux-gnu-nptl/csu/  -Wl,--version-script=/var/tmp/portage/sys-libs/glibc-2.20-r2/work/build-x86-x86_64-p
c-linux-gnu-nptl/libc.map -Wl,-soname=libc.so.6 -Wl,-z,combreloc -Wl,-z,relro -nostdlib -nostartfiles -e __libc_main -Wl,-z,now -L/var/tmp/portage/sys-libs/glibc-2.20-r
2/work/build-x86-x86_64-pc-linux-gnu-nptl -L/var/tmp/portage/sys-libs/glibc-2.20-r2/work/build-x86-x86_64-pc-linux-gnu-nptl/math -L/var/tmp/portage/sys-libs/glibc-2.20-
r2/work/build-x86-x86_64-pc-linux-gnu-nptl/elf -L/var/tmp/portage/sys-libs/glibc-2.20-r2/work/build-x86-x86_64-pc-linux-gnu-nptl/dlfcn -L/var/tmp/portage/sys-libs/glibc
-2.20-r2/work/build-x86-x86_64-pc-linux-gnu-nptl/nss -L/var/tmp/portage/sys-libs/glibc-2.20-r2/work/build-x86-x86_64-pc-linux-gnu-nptl/nis -L/var/tmp/portage/sys-libs/g
libc-2.20-r2/work/build-x86-x86_64-pc-linux-gnu-nptl/rt -L/var/tmp/portage/sys-libs/glibc-2.20-r2/work/build-x86-x86_64-pc-linux-gnu-nptl/resolv -L/var/tmp/portage/sys-
libs/glibc-2.20-r2/work/build-x86-x86_64-pc-linux-gnu-nptl/crypt -L/var/tmp/portage/sys-libs/glibc-2.20-r2/work/build-x86-x86_64-pc-linux-gnu-nptl/nptl -Wl,-rpath-link=
/var/tmp/portage/sys-libs/glibc-2.20-r2/work/build-x86-x86_64-pc-linux-gnu-nptl:/var/tmp/portage/sys-libs/glibc-2.20-r2/work/build-x86-x86_64-pc-linux-gnu-nptl/math:/va
r/tmp/portage/sys-libs/glibc-2.20-r2/work/build-x86-x86_64-pc-linux-gnu-nptl/elf:/var/tmp/portage/sys-libs/glibc-2.20-r2/work/build-x86-x86_64-pc-linux-gnu-nptl/dlfcn:/
var/tmp/portage/sys-libs/glibc-2.20-r2/work/build-x86-x86_64-pc-linux-gnu-nptl/nss:/var/tmp/portage/sys-libs/glibc-2.20-r2/work/build-x86-x86_64-pc-linux-gnu-nptl/nis:/
var/tmp/portage/sys-libs/glibc-2.20-r2/work/build-x86-x86_64-pc-linux-gnu-nptl/rt:/var/tmp/portage/sys-libs/glibc-2.20-r2/work/build-x86-x86_64-pc-linux-gnu-nptl/resolv
:/var/tmp/portage/sys-libs/glibc-2.20-r2/work/build-x86-x86_64-pc-linux-gnu-nptl/crypt:/var/tmp/portage/sys-libs/glibc-2.20-r2/work/build-x86-x86_64-pc-linux-gnu-nptl/n
ptl -o /var/tmp/portage/sys-libs/glibc-2.20-r2/work/build-x86-x86_64-pc-linux-gnu-nptl/libc.so -T /var/tmp/portage/sys-libs/glibc-2.20-r2/work/build-x86-x86_64-pc-linux
-gnu-nptl/shlib.lds /var/tmp/portage/sys-libs/glibc-2.20-r2/work/build-x86-x86_64-pc-linux-gnu-nptl/csu/abi-note.o /var/tmp/portage/sys-libs/glibc-2.20-r2/work/build-x8
6-x86_64-pc-linux-gnu-nptl/elf/soinit.os /var/tmp/portage/sys-libs/glibc-2.20-r2/work/build-x86-x86_64-pc-linux-gnu-nptl/libc_pic.os /var/tmp/portage/sys-libs/glibc-2.2
0-r2/work/build-x86-x86_64-pc-linux-gnu-nptl/elf/sofini.os /var/tmp/portage/sys-libs/glibc-2.20-r2/work/build-x86-x86_64-pc-linux-gnu-nptl/elf/interp.os /var/tmp/portag
e/sys-libs/glibc-2.20-r2/work/build-x86-x86_64-pc-linux-gnu-nptl/elf/ld.so -lgcc
/usr/lib/gcc/x86_64-pc-linux-gnu/4.8.5/../../../../x86_64-pc-linux-gnu/bin/ld: /var/tmp/portage/sys-libs/glibc-2.20-r2/work/build-x86-x86_64-pc-linux-gnu-nptl/libc_pic.
os: warning: relocation against `_dl_sysinfo' in readonly section `.text.compat'.
/var/tmp/portage/sys-libs/glibc-2.20-r2/work/build-x86-x86_64-pc-linux-gnu-nptl/libc_pic.os: In function `__GI_kill':
(.text+0x14af1): undefined reference to `_dl_sysinfo'
/var/tmp/portage/sys-libs/glibc-2.20-r2/work/build-x86-x86_64-pc-linux-gnu-nptl/libc_pic.os: In function `__sigaltstack':
(.text+0x150b1): undefined reference to `_dl_sysinfo'
/var/tmp/portage/sys-libs/glibc-2.20-r2/work/build-x86-x86_64-pc-linux-gnu-nptl/libc_pic.os: In function `__getcontext':
(.text+0x268b1): undefined reference to `_dl_sysinfo'
/var/tmp/portage/sys-libs/glibc-2.20-r2/work/build-x86-x86_64-pc-linux-gnu-nptl/libc_pic.os: In function `setcontext':
(.text+0x268f6): undefined reference to `_dl_sysinfo'
/var/tmp/portage/sys-libs/glibc-2.20-r2/work/build-x86-x86_64-pc-linux-gnu-nptl/libc_pic.os: In function `swapcontext':
(.text+0x26a14): undefined reference to `_dl_sysinfo'
/var/tmp/portage/sys-libs/glibc-2.20-r2/work/build-x86-x86_64-pc-linux-gnu-nptl/libc_pic.os:(.text+0x46f91): more undefined references to `_dl_sysinfo' follow
/usr/lib/gcc/x86_64-pc-linux-gnu/4.8.5/../../../../x86_64-pc-linux-gnu/bin/ld: warning: creating a DT_TEXTREL in object.
collect2: error: ld returned 1 exit status
../Makerules:601: recipe for target '/var/tmp/portage/sys-libs/glibc-2.20-r2/work/build-x86-x86_64-pc-linux-gnu-nptl/libc.so' failed

我们试图在另一台Gentoo机器上找到对_dl_sysinfo的引用，但没有结果：

xxxxxx ~ # find /lib64/ -name "*.so" -exec strings {} \; | grep dl_sysinfo
xxxxxx ~ # find /usr/lib64/ -name "*.so" -exec strings {} \; | grep dl_sysinfo
xxxxxx ~ # 

我们还试图将-fPIC -DPIC添加到CFLAGS中，但错误仍然存在。我们不知道为什么必须更新glibc包，因为我们已经使用PORTAGE_BINHOST安装了最新的包。gcc也是如此。

问题是:如何解决这个问题？

更新:我刚刚注意到将配置文件从hardened/linux/amd64切换到default/linux/amd64/13.0防止了glibc的出现，但这只是暂时的修复。我们绝对想保持强硬的形象。

Answer 1

如果gcc没有强硬的使用旗子，正在崛起的滑翔者就会失败。我在一些服务器上也遇到过这种情况，因为HHVM与强硬的gcc有问题。解决方案也是为sys/glibc指定"-hardened“。