Processing of gcc-defaults-ports_1.201_source.changes

gcc-defaults-ports_1.201_source.changes uploaded successfully to localhost along with the files: gcc-defaults-ports_1.201.dsc gcc-defaults-ports_1.201.tar.xz gcc-defaults-ports_1.201_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)

Processing of gcc-defaults_1.201_source.changes

gcc-defaults_1.201_source.changes uploaded successfully to localhost along with the files: gcc-defaults_1.201.dsc gcc-defaults_1.201.tar.xz gcc-defaults_1.201_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)

gcc-defaults_1.201_source.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 31 Aug 2022 10:25:04 +0200 Source: gcc-defaults Architecture: source Version: 1.201 Distribution: unstable Urgency: medium Maintainer: Debian GCC Maintainers Changed-By: Matthias Klose Changes: gcc-defaults (1.

gcc-defaults-ports_1.201_source.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 31 Aug 2022 10:19:40 +0200 Source: gcc-defaults-ports Architecture: source Version: 1.201 Distribution: unstable Urgency: medium Maintainer: Debian GCC Maintainers Changed-By: Matthias Klose Changes: gcc-defaul

Bug#1018799: gcc-12: Workround for fixing -latomic issue on riscv64 after glibc2.34

Hi, On 2022-08-31 08:04, Bo YU wrote: > Source: gcc-12 > Version: 12.2.0-1 > Severity: important > X-Debbugs-Cc: debian-ri...@lists.debian.org > > Dear gcc Maintainer, > > Since glibc 2.34 we need to link libatomic explicitly to fix > huge amount issues that has ftbfs on riscv64. > > The detail