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 [1]. See also the upstream discussion here [2].
> 
> Is this patch enough, or do we have to backport this [1] as well?
> 
> [1] https://gitlab.haskell.org/ghc/ghc/-/commit/fc186b0c0ac56d6ff6225d3f6607be37770fcb52

I am not 100% sure. I think I had the patch applied when I tested this.

> > While this patch fixes the original problem, the stage2 build later
> > fails due to memory exhaustion for which I haven't found a solution
> > yet.
> 
> I faced the same issue on mipsel (see [2]) and never found a solution
> for it. Luckily, mipsel got removed from release architectures.
> 
> [2] https://lists.debian.org/debian-mips/2023/07/msg00057.html

I see. Surprisingly, we don't run into memory issues on hppa and powerpc,
most likely because the buildds are running on 64-bit kernels.

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer
`. `'   Physicist
  `-    GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913