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

Hi, On 2022-09-06 09:56, Bo YU wrote: > Hi, > On Wed, Aug 31, 2022 at 07:04:53PM +0200, Aurelien Jarno wrote: > ... > > reason for limiting the link with -latomic to pthread, but that has been > > discussed internally before the patch submission to GCC, and has been > > lost. > > > > Anyway this

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

Hi, On Wed, Aug 31, 2022 at 07:04:53PM +0200, Aurelien Jarno wrote: ... reason for limiting the link with -latomic to pthread, but that has been discussed internally before the patch submission to GCC, and has been lost. Anyway this is probably something to try, but the way is done in Arch,

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

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

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 detailed explanation is here[0]: ``` ... linking with -pthread