From: Paul Eggert <eggert@cs.ucla.edu>
To: 24857@debbugs.gnu.org
Subject: bug#24857: Fwd: Re: emacs24/25 FTBFS since a long time on GNU/Hurd
Date: Wed, 2 Nov 2016 09:43:41 -0700 [thread overview]
Message-ID: <c1e9c427-e268-d737-3905-2a0ede0c8904@cs.ucla.edu> (raw)
In-Reply-To: <83oa1xnb5k.fsf@gnu.org>
-------- Forwarded Message --------
Subject: Re: emacs24/25 FTBFS since a long time on GNU/Hurd
Date: Wed, 02 Nov 2016 17:39:51 +0200
From: Eli Zaretskii <eliz@gnu.org>
Reply-To: Eli Zaretskii <eliz@gnu.org>
To: svante.signell@gmail.com
CC: emacs-devel@gnu.org
> From: Svante Signell <svante.signell@gmail.com>
> Date: Wed, 02 Nov 2016 15:16:54 +0100
>
> First time I compiled emacs 25.1 from upstream it passed, second time not.
> Compiling Debian versions almost always fail. Moslty the build fails with temacs
> failing to execute: Killed. In my opionion it's a real loss not to gave a modern
> version of emacs25 available for use in GNU/Hurd (not everybody use vi).
>
> Do anybody of you have an idea on how to solve this problem?
My suggestion is to run the failing temacs command line under GDB and
see where it crashes.
The best way to communicate this information is to file a bug report,
using "M-x report-emacs-bug RET" (in some version of Emacs you have
that is operable; if not, just email the details to
bug-gnu-emacs@gnu.org).
next parent reply other threads:[~2016-11-02 16:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1478096214.16249.46.camel@gmail.com>
[not found] ` <83oa1xnb5k.fsf@gnu.org>
2016-11-02 16:43 ` Paul Eggert [this message]
[not found] ` <1478101904.16249.56.camel@gmail.com>
2016-11-02 16:44 ` bug#24857: Fwd: Re: emacs24/25 FTBFS since a long time on GNU/Hurd Paul Eggert
2016-12-02 10:35 ` bug#24857: " Svante Signell
[not found] ` <1480674949.16952.8.camel@gmail.com>
2016-12-03 0:02 ` Paul Eggert
2016-12-07 22:40 ` Svante Signell
2016-12-08 1:15 ` Daniel Colascione
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=c1e9c427-e268-d737-3905-2a0ede0c8904@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=24857@debbugs.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 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).