Re: Bug#1052144: ghc: Needs to link against libatomic on at least m68k

Hello! On Sat, 2023-10-14 at 16:37 +0200, John Paul Adrian Glaubitz wrote: > Hi! > > On Sat, 2023-10-14 at 17:33 +0300, Ilias Tsitsimpis wrote: > > As a side note, I believe the attached patch is wrong, it changes the > > semantics of the functions. Notice that __sync_val_compare_and_swap() > > r

Re: Bug#1052144: ghc: Needs to link against libatomic on at least m68k

Hi! On Sat, 2023-10-14 at 17:33 +0300, Ilias Tsitsimpis wrote: > As a side note, I believe the attached patch is wrong, it changes the > semantics of the functions. Notice that __sync_val_compare_and_swap() > returns the initial value of the variable x, whereas > __atomic_compare_exchange() return

Re: Bug#1052144: ghc: Needs to link against libatomic on at least m68k

Hi Adrian, On Sat, Oct 14, 2023 at 11:35AM, John Paul Adrian Glaubitz wrote: > Attaching an updated version of the patch which applies against the 9.4.7-1 > version of the ghc package. Would be nice if it could be included for the > next upload. Thanks for the reminder, I will include this in the

Re: Bug#1052144: ghc: Needs to link against libatomic on at least m68k

Hello! On Fri, 2023-09-22 at 09:20 +0200, John Paul Adrian Glaubitz wrote: > The attached patch fixes the issue for me. The underlying problem is > the use of legacy atomic functions for which no 64-bit variants exist > on some architectures [1]. See also the upstream discussion here [2]. Attachi

Re: Bug#1052144: ghc: Needs to link against libatomic on at least m68k

On Wed, 2023-09-27 at 22:00 +0300, Ilias Tsitsimpis wrote: > On Fri, Sep 22, 2023 at 09:20AM, John Paul Adrian Glaubitz wrote: > > The attached patch fixes the issue for me. The underlying problem is > > the use of legacy atomic functions for which no 64-bit variants exist > > on some architectures

Re: Bug#1052144: ghc: Needs to link against libatomic on at least m68k

Hi Adrian, On Fri, Sep 22, 2023 at 09:20AM, John Paul Adrian Glaubitz wrote: > The attached patch fixes the issue for me. The underlying problem is > the use of legacy atomic functions for which no 64-bit variants exist > on some architectures [1]. See also the upstream discussion here [2]. Is th

Re: Bug#1052144: ghc: Needs to link against libatomic on at least m68k

Control: tags -1 +patch Hi! The attached patch fixes the issue for me. The underlying problem is the use of legacy atomic functions for which no 64-bit variants exist on some architectures [1]. See also the upstream discussion here [2]. While this patch fixes the original problem, the stage2 bui

Bug#1052144: ghc: Needs to link against libatomic on at least m68k

Source: ghc Version: 9.4.6-1 Severity: normal User: debian-68k@lists.debian.org Usertags: m68k X-Debbugs-Cc: debian-68k@lists.debian.org Hello! On m68k, building ghc fails with: "inplace/bin/ghc-stage1" -o utils/iserv/stage2_p/build/tmp/ghc-iserv-prof -hisuf p_hi -osuf p_o -hcsuf p_hc -static