From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Efraim Flashner <efraim@flashner.co.il>
Cc: 34427@debbugs.gnu.org, "Ludovic Courtès" <ludo@gnu.org>,
"GNU Debbugs" <control@debbugs.gnu.org>
Subject: bug#34427: guile-bootstrap@2.2 segfault?
Date: Fri, 07 Oct 2022 22:46:39 -0400 [thread overview]
Message-ID: <87a6673ucw.fsf@gmail.com> (raw)
In-Reply-To: <Ylc6LgVZ80CupiQ2@pbp> (Efraim Flashner's message of "Thu, 14 Apr 2022 00:01:34 +0300")
tags 34427 -important
thanks
Hi,
Efraim Flashner <efraim@flashner.co.il> writes:
[...]
>> Besides, if PPC32 is the only platform that has a problem, I think this
>> bug should not be a blocker.
>>
>> WDYT?
>>
>> Ludo’.
>
> Here's what I get from strace when running on bare metal. I agree, if
> it's only affecting ppc32 we shouldn't have it be a blocker.
I'd removing the important flag since this appears to affect only ppc32
architecture and has been dormant for years.
Thanks,
Maxim
prev parent reply other threads:[~2022-10-08 2:47 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 ` bug#34427: bug#34453: " zimoun
2022-04-13 21:07 ` [bug#34453] " 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 [this message]
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=87a6673ucw.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=34427@debbugs.gnu.org \
--cc=control@debbugs.gnu.org \
--cc=efraim@flashner.co.il \
--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.