This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug other/78096] New: gcc-4.9.4 make bootstrap libgcc_s.so link problem
- From: "edeveaud at pasteur dot fr" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Mon, 24 Oct 2016 13:33:53 +0000
- Subject: [Bug other/78096] New: gcc-4.9.4 make bootstrap libgcc_s.so link problem
- Auto-submitted: auto-generated
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78096
Bug ID: 78096
Summary: gcc-4.9.4 make bootstrap libgcc_s.so link problem
Product: gcc
Version: 4.9.4
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: other
Assignee: unassigned at gcc dot gnu.org
Reporter: edeveaud at pasteur dot fr
Target Milestone: ---
Hello,
while building gcc-4.9.4 on centos6 I have a strange link problem
some libraries are linked to the installed libgcc_s.so libraries, while other
are linked to libgcc_s.so system libraries
eg:
link to system libgcc_s.so
libstdc++.so
libvtv.so
libitm.so
link to installed libgcc_s.so
libasan.so
liblsan.so
libcilkrts.so
libtsan.so
libubsan.so
here is a Dockerfile that reproduce the problem.
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
FROM centos:6
MAINTAINER Eric Deveaud <edeveaud@pasteur.fr>
RUN yum install -y gcc gcc-c++ wget
WORKDIR /src
#---- install internal gcc
RUN mkdir -p gcc/4.9.4 && \
cd gcc/4.9.4 && \
wget -qO- ftp://ftp.lip6.fr/pub/gcc/releases/gcc-4.9.4/gcc-4.9.4.tar.gz |
tar xz --strip-components 1 && \
sh contrib/download_prerequisites
RUN mkdir -p /tmp/build && \
cd /tmp/build && \
/src/gcc/4.9.4/configure --disable-multilib --enable-threads=posix
--enable-__cxa_atexit -enable-languages=c,c++ --prefix=/exe/gcc/4.9.4 && \
make bootstrap && \
make install
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
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.
find /exe/gcc/4.9.4 -type l -name \*.so | xargs ldd | grep libgcc_s.so
libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007f043971c000)
libgcc_s.so.1 => /exe/gcc/4.9.4/lib/../lib64/libgcc_s.so.1
(0x00007f7ae4b97000)
libgcc_s.so.1 => /exe/gcc/4.9.4/lib/../lib64/libgcc_s.so.1
(0x00007f4321ef7000)
libgcc_s.so.1 => /exe/gcc/4.9.4/lib/../lib64/libgcc_s.so.1
(0x00007fd9918fe000)
libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007f5ea3ba4000)
libgcc_s.so.1 => /exe/gcc/4.9.4/lib/../lib64/libgcc_s.so.1
(0x00007fbaf49bc000)
libgcc_s.so.1 => /exe/gcc/4.9.4/lib/../lib64/libgcc_s.so.1
(0x00007fd7f5423000)
libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007f57bcfeb000)
did I missed something ?
best regards
Eric