unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Rob Browning <rlb@defaultvalue.org>
Cc: 57789@debbugs.gnu.org
Subject: bug#57789: Emacs 28.1 clone build with native compilation crashes on s390x
Date: Wed, 14 Sep 2022 05:42:19 +0300	[thread overview]
Message-ID: <83tu5a3cdw.fsf@gnu.org> (raw)
In-Reply-To: <87h71aix5r.fsf@trouble.defaultvalue.org> (message from Rob Browning on Tue, 13 Sep 2022 20:04:32 -0500)

> From: Rob Browning <rlb@defaultvalue.org>
> Date: Tue, 13 Sep 2022 20:04:32 -0500
> 
> On zelenka.debian.org https://db.debian.org/machines.cgi?host=zelenka
> the build crashes with a segfault with current Debian sid (unstable).  I
> can produce the crash like this:
> 
>   git clone --single-branch --branch emacs-28 .../emacs.git

If you build the current emacs-28 branch, then it isn't Emacs 28.1,
it's Emacs 28.2.50, right?

>   cd emacs
>   ./autogen.sh
>   ./configure --prefix=/home/rlb/opt/emacs-tmp --with-native-compilation
>   make check
> 
> The debian package produced a similar failure earlier:
> 
>   https://buildd.debian.org/status/fetch.php?pkg=emacs&arch=s390x&ver=1%3A28.1%2B1-3&stamp=1662863442&raw=0
> 
> Here's the final bit of the clone build's log, and I'm happy to help
> test on the machine if that'd be useful:

Please run the crashing command under GDB, and when it segfaults,
produce the C-level and Lisp-level backtrace, and post them here.

Thanks.





  reply	other threads:[~2022-09-14  2:42 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-14  1:04 bug#57789: Emacs 28.1 clone build with native compilation crashes on s390x Rob Browning
2022-09-14  2:42 ` Eli Zaretskii [this message]
2022-09-14  3:06   ` Rob Browning
2022-09-14  3:20     ` Rob Browning
2022-09-14 20:19   ` Rob Browning
2022-09-14 20:21     ` Rob Browning
2022-09-16  6:04       ` Gerd Möllmann
2022-09-17 21:04         ` Rob Browning
2022-09-18  5:22           ` Gerd Möllmann
2022-09-18  5:49             ` Eli Zaretskii
2022-09-18  5:55               ` Gerd Möllmann
2022-09-18  5:33           ` Eli Zaretskii
2022-09-24 21:06             ` Rob Browning
2023-06-07 21:15               ` Andrea Corallo
2023-09-11 18:08                 ` Stefan Kangas
2022-09-15  7:10     ` Eli Zaretskii
2022-09-15 14:51       ` Paul Eggert via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-15 16:26         ` Rob Browning
2022-09-16  8:43         ` Andrea Corallo
2022-09-16  8:39       ` Andrea Corallo
2022-09-17 21:00       ` Rob Browning

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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=83tu5a3cdw.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=57789@debbugs.gnu.org \
    --cc=rlb@defaultvalue.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 public inbox

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).