From: Eli Zaretskii <eliz@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: okshirai@gmail.com, 26638@debbugs.gnu.org
Subject: bug#26638: 25.2; Fatal error 6: Abortmake[1]: *** [Makefile:737: bootstrap-emacs] Abort (core dumped)
Date: Sat, 02 Sep 2017 15:31:10 +0300 [thread overview]
Message-ID: <83val1z3ht.fsf@gnu.org> (raw)
In-Reply-To: <f4f0eea5-4b9b-a23d-9bf0-19481dabd978@cs.ucla.edu> (message from Paul Eggert on Sat, 29 Apr 2017 12:21:49 -0700)
unblock 24655 by 26638
thanks
> From: Paul Eggert <eggert@cs.ucla.edu>
> Date: Sat, 29 Apr 2017 12:21:49 -0700
> Cc: 26638@debbugs.gnu.org
>
> For what it's worth I could not reproduce the problem on i386-pc-solaris2.11
> with Sun C 5.12. Emacs did not crash at all.
>
> My guess is that it's a bug in how unexec works in your environment. It's also
> possible that it's a bug in your C compiler, though I think this less likely.
> Unfortunately, it is hard to debug this sort of thing without access to the
> failing system.
>
> Is it easy for you to try the latest C compiler from Oracle instead? The current
> stable version is Sun C 5.14 (Oracle Developer Studio 12.5), which you can get here:
>
> https://www.oracle.com/tools/developerstudio/index.html
Any news on this one?
In any case, given the time since the last communication, and no
similar reports from anyone else, it doesn't seem right to block the
release of Emacs 26.1 due to this problem.
Thanks.
next prev parent reply other threads:[~2017-09-02 12:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-24 14:20 bug#26638: 25.2; Fatal error 6: Abortmake[1]: *** [Makefile:737: bootstrap-emacs] Abort (core dumped) 白井彰
2017-04-25 0:57 ` Paul Eggert
2017-04-25 15:50 ` 白井彰
2017-04-29 19:21 ` Paul Eggert
2017-09-02 12:31 ` Eli Zaretskii [this message]
2017-09-02 13:03 ` 白井彰
2017-09-02 18:18 ` Paul Eggert
2017-09-13 13:17 ` 白井彰
2017-09-13 15:26 ` Paul Eggert
2017-09-14 15:11 ` 白井彰
2017-09-14 19:14 ` Paul Eggert
2017-09-27 15:16 ` 白井彰
2017-10-02 6:18 ` Paul Eggert
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=83val1z3ht.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=26638@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=okshirai@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).