From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: ann.onymous@orange.fr, 43152@debbugs.gnu.org
Subject: bug#43152: 28.0.50; when building emacs 28.0.50 ./temacs is stopped with core
Date: Tue, 01 Sep 2020 17:29:04 +0300 [thread overview]
Message-ID: <83eenlwoy7.fsf@gnu.org> (raw)
In-Reply-To: <CADwFkmkROeNY2Akj0h7er-Lbi80s74gDJw+9mBMf=T1UNB_Y3Q@mail.gmail.com> (message from Stefan Kangas on Tue, 1 Sep 2020 04:10:12 -0700)
> From: Stefan Kangas <stefankangas@gmail.com>
> Date: Tue, 1 Sep 2020 04:10:12 -0700
>
> Philippe Spiesser <ann.onymous@orange.fr> writes:
>
> > Hello,
> > yesterday, I have updated the local directory of emacs 28.0.50 to
> > rebuild a new version; the last time I've updated was the 9 of august
> > and everything was OK.
> > Building stops with the messages :
> > cp -f temacs bootstrap-emacs
> > rm -f bootstrap-emacs.pdmp
> > ./temacs --batch -l loadup --temacs=pbootstrap
> > make[1]: *** [bootstrap-emacs.pdmp] Segmentation fault: 11
> > make: *** [src] Error 2
> > I can't explain this.
> > I hope it's the correct place to send this message
>
> Did you try "make bootstrap"?
>
> Also, please include the full commands you used to build this, starting
> with configure.
If "make bootstrap" doesn't help, please run the command which crashes
under GDB, and when it crashes, produce the backtrace and post it
here.
next prev parent reply other threads:[~2020-09-01 14:29 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-01 9:37 bug#43152: 28.0.50; when building emacs 28.0.50 ./temacs is stopped with core Philippe Spiesser
2020-09-01 11:10 ` Stefan Kangas
2020-09-01 14:19 ` Anonymous
2020-09-01 14:29 ` Eli Zaretskii [this message]
2020-09-01 16:49 ` Anonymous
2020-09-01 17:09 ` Eli Zaretskii
2020-09-01 17:15 ` Stefan Kangas
2020-09-02 10:00 ` Anonymous
2020-09-06 14:31 ` Mattias Engdegård
2020-09-06 14:38 ` Lars Ingebrigtsen
2020-09-06 15:44 ` Mattias Engdegård
2020-09-06 23:07 ` Lars Ingebrigtsen
2020-09-07 7:25 ` Mattias Engdegård
2020-09-07 10:20 ` Lars Ingebrigtsen
2020-09-07 12:24 ` Angelo Graziosi
2020-09-07 12:58 ` Anonymous
[not found] <1457551226.863660.1599040446670@mail1.libero.it>
[not found] ` <CADwFkmnymz3jBD41GjfONHAreqQgYDN2-5+sPfzEg5V0Yh=M=w@mail.gmail.com>
2020-09-02 20:09 ` Paul Eggert
2020-09-03 12:30 ` Anonymous
2020-09-03 15:35 ` Angelo Graziosi
2020-09-03 19:17 ` Paul Eggert
2020-09-03 23:17 ` Angelo Graziosi
2020-09-03 23:53 ` Angelo Graziosi
2020-09-04 20:32 ` Paul Eggert
2020-09-04 21:24 ` Angelo Graziosi
2020-09-04 21:34 ` Angelo Graziosi
2020-09-04 21:56 ` Paul Eggert
2020-09-05 6:30 ` Angelo Graziosi
2020-09-05 12:05 ` Lars Ingebrigtsen
2020-09-05 19:27 ` Paul Eggert
2020-09-05 21:30 ` Lars Ingebrigtsen
2020-09-06 0:58 ` Paul Eggert
2020-09-06 11:50 ` Lars Ingebrigtsen
2020-09-05 21:36 ` Lars Ingebrigtsen
2020-09-05 21:41 ` Lars Ingebrigtsen
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=83eenlwoy7.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=43152@debbugs.gnu.org \
--cc=ann.onymous@orange.fr \
--cc=stefankangas@gmail.com \
/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).