https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78097
Bug ID: 78097 Summary: gcc-6.2.0 inconsistent libgcc_s.so link Product: gcc Version: 6.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: other Assignee: unassigned at gcc dot gnu.org Reporter: edeveaud at pasteur dot fr Target Milestone: --- Hello, building gcc-6.2.0 on centos6 lead on inconsistent link to libgcc_s.so some libraries are linked to the installed libraries, while other are linked to libgcc_s.so system libraries here is a Dockerfile that reproduce the problem. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- FROM centos:6 MAINTAINER Eric Deveaud <edeve...@pasteur.fr> RUN yum install -y gcc gcc-c++ wget WORKDIR /src #---- install internal gcc RUN mkdir -p gcc/6.2.0 && \ cd gcc/6.2.0 && \ wget -qO- ftp://ftp.lip6.fr/pub/gcc/releases/gcc-6.2.0/gcc-6.2.0.tar.gz | tar xz --strip-components 1 && \ sh contrib/download_prerequisites RUN mkdir -p /tmp/build && \ cd /tmp/build && \ /src/gcc/6.2.0/configure --disable-multilib --enable-threads=posix --enable-__cxa_atexit -enable-languages=c,c++ --prefix=/exe/gcc/6.2.0 && \ MAKEFLAGS="-j $(grep -c ^processor /proc/cpuinfo)" make bootstrap && \ make install # run produced docker using # docker run -i -t gcc /bin/bash # then # find /exe/gcc/4.9.4 -type l -name \*.so | xargs ldd | grep libgcc_s.so -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- container was built using docker build -f Dockerfile-gcc -t gcc . | tee log (I can provide buil log) and then container run using docker run -i -t gcc /bin/bash following command emphasis the linking problem. [root@5ec47cdc07e6 src]# find /exe/gcc/6.2.0/ -type l -name \*.so | xargs ldd | grep libgcc_s.so libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007ff1dde2e000) libgcc_s.so.1 => /exe/gcc/6.2.0/lib/../lib64/libgcc_s.so.1 (0x00007f1be06c7000) libgcc_s.so.1 => /exe/gcc/6.2.0/lib/../lib64/libgcc_s.so.1 (0x00007f6490629000) libgcc_s.so.1 => /exe/gcc/6.2.0/lib/../lib64/libgcc_s.so.1 (0x00007f7afcaf3000) libgcc_s.so.1 => /exe/gcc/6.2.0/lib/../lib64/libgcc_s.so.1 (0x00007febfaf18000) libgcc_s.so.1 => /exe/gcc/6.2.0/lib/../lib64/libgcc_s.so.1 (0x00007fbe2165c000) libgcc_s.so.1 => /exe/gcc/6.2.0/lib/../lib64/libgcc_s.so.1 (0x00007f18d26f8000) libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007f2390256000) libgcc_s.so.1 => /exe/gcc/6.2.0/lib/../lib64/libgcc_s.so.1 (0x00007f9755e8a000) /exe/gcc/6.2.0/lib64/libstdc++.so /exe/gcc/6.2.0/lib64/libitm.so links to /lib64/libgcc_s.so.1 /exe/gcc/6.2.0/lib64/libasan.so /exe/gcc/6.2.0/lib64/liblsan.so /exe/gcc/6.2.0/lib64/libcilkrts.so /exe/gcc/6.2.0/lib64/libtsan.so /exe/gcc/6.2.0/lib64/libubsan.so /exe/gcc/6.2.0/lib64/libcc1.so /exe/gcc/6.2.0/lib/gcc/x86_64-pc-linux-gnu/6.2.0/plugin/libcc1plugin.so links to /exe/gcc/6.2.0/lib/../lib64/libgcc_s.so.1 NB see also: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78096 @Markus I hope that gcc-6.0.2 is still maintained ;-) best regards Eric