GNU bug report logs - #40164
Fix for libgccjit

Previous Next

Package: guix-patches;

Reported by: Formbi <formbi <at> protonmail.com>

Date: Sat, 21 Mar 2020 13:14:02 UTC

Severity: normal

Tags: moreinfo

Done: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
Cc: tracker <at> debbugs.gnu.org
Subject: bug#40164: closed (Fix for libgccjit)
Date: Sat, 22 Feb 2025 12:55:03 +0000
[Message part 1 (text/plain, inline)]
Your message dated Sat, 22 Feb 2025 21:54:17 +0900
with message-id <8734g6uoli.fsf <at> gmail.com>
and subject line Re: bug#40164: Fix for libgccjit
has caused the debbugs.gnu.org bug report #40164,
regarding Fix for libgccjit
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)


-- 
40164: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=40164
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems
[Message part 2 (message/rfc822, inline)]
From: Formbi <formbi <at> protonmail.com>
To: "guix-patches <at> gnu.org" <guix-patches <at> gnu.org>
Subject: Fix for libgccjit
Date: Sat, 21 Mar 2020 13:13:18 +0000
[Message part 3 (text/plain, inline)]
Empty Message
[0001-fix-libgccjit.patch (text/x-patch, attachment)]
[Message part 5 (message/rfc822, inline)]
From: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
To: Simon Tournier <zimon.toutoune <at> gmail.com>
Cc: 40164-done <at> debbugs.gnu.org, Formbi <formbi <at> protonmail.com>,
 Ludovic Courtès <ludo <at> gnu.org>
Subject: Re: bug#40164: Fix for libgccjit
Date: Sat, 22 Feb 2025 21:54:17 +0900
Hi,

Simon Tournier <zimon.toutoune <at> gmail.com> writes:

> Hi,
>
> For reference: https://issues.guix.gnu.org/issue/40164
>
> On Wed, 14 Jul 2021 at 12:50, Maxim Cournoyer <maxim.cournoyer <at> gmail.com> wrote:
>> Maxim Cournoyer <maxim.cournoyer <at> gmail.com> writes:
>>
>>> Perhaps the original issue is the one reported/fix with a patch here [0]
>>> ?  Formbi, could you share a simple reproducer so that we can test if
>>> the patches resolve it?  It seems it'd be useful to upstream as well (to
>>> have a reproducer).
>>>
>>> Thanks!
>>>
>>> [0]  https://gcc.gnu.org/legacy-ml/gcc-patches/2019-03/msg01045.html
>>
>> Another data point: this seems to be worked around in Nix using the fix
>> proposed by Formbi:
>> https://github.com/NixOS/nixpkgs/blob/8a815af4280f3e0d5ff740faa7d489e2b9e36829/pkgs/applications/editors/emacs/generic.nix#L87.
>
> What is the status of all this?  The report is marked as moreinfo and
> the last activity is very old.  I’m in favor to close.  WDYT?

Me too.  Done.

-- 
Thanks,
Maxim


This bug report was last modified 89 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.