Bug#950550: libgcc1: upgrade from 1:9.2.1-25 to libgcc1 1:10-20200202-1 breaks gcc
control: reopen -1
control: severity -1 serious
control: found -1 gcc-10/10-20200202-1
control: found -1 gcc-10/10-20200204-1
On 2020-02-04 15:19, Debian FTP Masters wrote:
> Source: gcc-10
> Source-Version: 10-20200204-1
>
> We believe that the bug you reported is fixed in the latest version of
> gcc-10, which is due to be installed in the Debian FTP archive.
>
> A summary of the changes between this version and the previous one is
> attached.
>
> Thank you for reporting the bug, which will now be closed. If you
> have further comments please address them to 950550@bugs.debian.org,
> and the maintainer will reopen the bug report if appropriate.
>
> Debian distribution maintenance software
> pp.
> Matthias Klose <doko@debian.org> (supplier of updated gcc-10 package)
>
> (This message was generated automatically at their request; if you
> believe that there is a problem with it please contact the archive
> administrators by mailing ftpmaster@ftp-master.debian.org)
>
>
> We believe that the bug you reported is fixed in the latest version of
> gcc-10, which is due to be installed in the Debian FTP archive.
>
> A summary of the changes between this version and the previous one is
> attached.
>
> Thank you for reporting the bug, which will now be closed. If you
> have further comments please address them to 950550@bugs.debian.org,
> and the maintainer will reopen the bug report if appropriate.
>
> Debian distribution maintenance software
> pp.
> Matthias Klose <doko@debian.org> (supplier of updated gcc-10 package)
>
> (This message was generated automatically at their request; if you
> believe that there is a problem with it please contact the archive
> administrators by mailing ftpmaster@ftp-master.debian.org)
>
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> Format: 1.8
> Date: Tue, 04 Feb 2020 15:52:16 +0100
> Source: gcc-10
> Architecture: source
> Version: 10-20200204-1
> Distribution: unstable
> Urgency: medium
> Maintainer: Debian GCC Maintainers <debian-gcc@lists.debian.org>
> Changed-By: Matthias Klose <doko@debian.org>
> Closes: 950550 950579
> Changes:
> gcc-10 (10-20200204-1) unstable; urgency=medium
> .
> * GCC snapshot, taken from the trunk (20200202, 0303907ea5d).
> * On architectures where libgcc_s.so is a symlink, replace the symlink with
> a simple linker script.
> * Add breaks on libgcc-N-dev packages on arm64, s390x and sparc64.
> Closes: #950550, #950579.
This is not enough. All architectures are affected when using gold.
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
--
Aurelien Jarno GPG: 4096R/1DDD8C9B
aurelien@aurel32.net http://www.aurel32.net
Reply to: