all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 34453@debbugs.gnu.org, 34427@debbugs.gnu.org
Subject: bug#34427: bug#34453: [PATCH] build guile-static with guile-2.0
Date: Tue, 12 Apr 2022 12:10:09 +0200	[thread overview]
Message-ID: <86o816394u.fsf_-_@gmail.com> (raw)
In-Reply-To: <87mumvhg5u.fsf@gnu.org> ("Ludovic Courtès"'s message of "Sat, 16 Feb 2019 17:06:05 +0100")

Hi,

What is the status of this old patch #34453?

http://issues.guix.gnu.org/issue/34453


On Sat, 16 Feb 2019 at 17:06, Ludovic Courtès <ludo@gnu.org> wrote:
> Efraim Flashner <efraim@flashner.co.il> skribis:
>
>> When experimenting I found that using guile@2.0 as a base for
>> guile-static, the resulting guile-static didn't segfault on the target
>> architecture.
>
> As discussed in <https://issues.guix.info/issue/34427>, I would rather
> fix the segfault in 2.2 than move back to 2.0 and effectively delay the
> problem.

Note that #34427 is still open.


Cheers,
simon




  reply	other threads:[~2022-04-12 10:17 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-11  9:11 bug#34427: guile-bootstrap@2.2 segfault? Efraim Flashner
2019-02-12  9:17 ` bug#34427: [PATCH] build guile-static with guile-2.0 Efraim Flashner
2019-02-16 16:06   ` bug#34427: [bug#34453] " Ludovic Courtès
2022-04-12 10:10     ` zimoun [this message]
2022-04-13 21:07       ` Efraim Flashner
2022-06-23  8:14         ` bug#34453: " zimoun
2019-02-12 14:27 ` bug#34427: guile-bootstrap@2.2 segfault? Ludovic Courtès
2019-02-12 15:44   ` Efraim Flashner
2022-04-12 10:12     ` zimoun
2022-04-12 16:01     ` Ludovic Courtès
2022-04-13 21:01       ` Efraim Flashner
2022-04-15  7:45         ` Ludovic Courtès
2022-06-23  8:17           ` zimoun
2022-10-18 16:14             ` zimoun
2022-10-18 16:22               ` Efraim Flashner
2022-10-19 10:40                 ` zimoun
2022-10-08  2:46         ` Maxim Cournoyer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=86o816394u.fsf_-_@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=34427@debbugs.gnu.org \
    --cc=34453@debbugs.gnu.org \
    --cc=ludo@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.