Bug#950715: marked as done (libgcc1: upgrade from 1:9.2.1-25 to libgcc1 1:10-20200202-1 breaks gcc with gold linker)
Your message dated Thu, 13 Feb 2020 08:52:00 +0000
with message-id <20200213085200.GA401697@espresso.pseudorandom.co.uk>
and subject line Re: Bug#950715: libgcc1: upgrade from 1:9.2.1-25 to libgcc1 1:10-20200202-1 breaks gcc with gold linker
has caused the Debian Bug report #950715,
regarding libgcc1: upgrade from 1:9.2.1-25 to libgcc1 1:10-20200202-1 breaks gcc with gold linker
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
950715: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950715
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: libgcc1
Version: 1:10-20200202-1
Severity: serious
Upgrading libgcc1 to version >= 10 on a system breaks gcc-7, gcc-8 and
gcc-9 when using the gold linker, as gcc passes the wrong path to the
libgcc_s.so.1 library. All architectures are affected, example on amd64,
starting from a bullseye chroot:
| $ gcc -fuse-ld=gold -o hello hello.c
| $ sudo apt-get install libgcc1
| Reading package lists... Done
| Building dependency tree
| Reading state information... Done
| The following additional packages will be installed:
| gcc-10-base libgcc-s1
| The following NEW packages will be installed:
| gcc-10-base libgcc-s1
| The following packages will be upgraded:
| libgcc1
| 1 upgraded, 2 newly installed, 0 to remove and 87 not upgraded.
| Need to get 278 kB of archives.
| After this operation, 381 kB of additional disk space will be used.
| Do you want to continue? [Y/n]
| Get:1 http://localhost:3142/debian sid/main amd64 gcc-10-base amd64 10-20200202-1 [195 kB]
| Get:2 http://localhost:3142/debian sid/main amd64 libgcc-s1 amd64 10-20200202-1 [41.6 kB]
| Get:3 http://localhost:3142/debian sid/main amd64 libgcc1 amd64 1:10-20200202-1 [41.6 kB]
| Fetched 278 kB in 0s (25.7 MB/s)
| debconf: delaying package configuration, since apt-utils is not installed
| Selecting previously unselected package gcc-10-base:amd64.
| (Reading database ... 35349 files and directories currently installed.)
| Preparing to unpack .../gcc-10-base_10-20200202-1_amd64.deb ...
| Unpacking gcc-10-base:amd64 (10-20200202-1) ...
| Setting up gcc-10-base:amd64 (10-20200202-1) ...
| Selecting previously unselected package libgcc-s1:amd64.
| (Reading database ... 35355 files and directories currently installed.)
| Preparing to unpack .../libgcc-s1_10-20200202-1_amd64.deb ...
| Unpacking libgcc-s1:amd64 (10-20200202-1) ...
| Setting up libgcc-s1:amd64 (10-20200202-1) ...
| (Reading database ... 35358 files and directories currently installed.)
| Preparing to unpack .../libgcc1_1%3a10-20200202-1_amd64.deb ...
| Unpacking libgcc1 (1:10-20200202-1) over (1:9.2.1-25) ...
| Setting up libgcc1 (1:10-20200202-1) ...
| Processing triggers for ccache (3.7.7-1) ...
| Updating symlinks in /usr/lib/ccache ...
| Processing triggers for libc-bin (2.29-9) ...
| $ gcc -fuse-ld=gold -o hello hello.c
| /usr/bin/ld.gold: error: cannot open /usr/lib/gcc/x86_64-linux-gnu/9/libgcc_s.so.1: No such file or directory
| /usr/bin/ld.gold: error: cannot open /usr/lib/gcc/x86_64-linux-gnu/9/libgcc_s.so.1: No such file or directory
| collect2: error: ld returned 1 exit status
| $
In turns this causes many autopktest failures:
https://ci.debian.net/data/autopkgtest/testing/amd64/d/deal.ii/4202144/log.gz
https://ci.debian.net/data/autopkgtest/testing/amd64/g/ghc/4202362/log.gz
https://ci.debian.net/data/autopkgtest/testing/amd64/h/haskell-hgettext/4202485/log.gz
https://ci.debian.net/data/autopkgtest/testing/amd64/h/haskell-hopenpgp/4202487/log.gz
libgcc-s1 probably misses a Break: against the older gcc-X versions.
--- End Message ---
--- Begin Message ---
Version: 1:10-20200211-1
On Wed, 05 Feb 2020 at 11:16:51 +0100, Aurelien Jarno wrote:
> Upgrading libgcc1 to version >= 10 on a system breaks gcc-7, gcc-8 and
> gcc-9 when using the gold linker, as gcc passes the wrong path to the
> libgcc_s.so.1 library.
This appears to have been fixed in unstable, most likely by
"libgcc-sN: Move library back to /lib from /usr/lib". Starting from a
bullseye environment:
root@host:~# apt-get install gcc-7 gcc-8 gcc-9
...
root@host:~# for x in 7 8 9; do gcc-$x -fuse-ld=gold -ohello hello.c; done
root@host:~# for x in 7 8 9; do gcc-$x -ohello hello.c; done
root@host:~# apt install libgcc1
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
gcc-10-base libgcc-s1
The following NEW packages will be installed:
gcc-10-base libgcc-s1
The following packages will be upgraded:
libgcc1
...
root@host:~# for x in 7 8 9; do gcc-$x -fuse-ld=gold -ohello hello.c; done
root@host:~# for x in 7 8 9; do gcc-$x -ohello hello.c; done
root@host:~# apt install gcc-10
...
root@host:~# for x in 7 8 9 10; do gcc-$x -ohello hello.c; done
root@host:~# for x in 7 8 9 10; do gcc-$x -fuse-ld=gold -ohello hello.c; done
--- End Message ---
Reply to: