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

Ilias Tsitsimpis <[email protected]>
Newsgroups gmane.linux.debian.ports.68k
Message-ID <[email protected]>
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 this patch enough, or do we have to backport this [1] as well?

[1] https://gitlab.haskell.org/ghc/ghc/-/commit/fc186b0c0ac56d6ff6225d3f6607be37770fcb52

> 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

Best,
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.