From: "Lennart Borgman (gmail)" <lennart.borgman@gmail.com>
To: Alan Mackenzie <acm@muc.de>
Cc: emacs-devel@gnu.org
Subject: Re: Fresh checkout: Seg fault whilst byte-compiling ../lisp/international/mule-cmds.el
Date: Fri, 30 May 2008 00:03:39 +0200 [thread overview]
Message-ID: <483F283B.3050602@gmail.com> (raw)
In-Reply-To: <20080529202056.GA10586@muc.de>
Alan Mackenzie wrote:
> Hi, Emacs!
>
> I recently did a fresh checkout (an equally recent cvs updated system
> having failed to build), where recently means today, Thursday 2008-05-29
> ~18:00 GMT.
>
> I tried to build it with:
>
> % ./configure --with-gif=no --with-tiff=no
> % make bootstrap
>
> It failed with:
>
> Compiling /home/acm/emacs/emacs.290508/lisp/international/mule-cmds.el
> Fatal error (11)make[3]: ***
> [/home/acm/emacs/emacs.290508/lisp/international/mule-cmds.elc]
> Segmentation fault
> make[3]: Leaving directory `/home/acm/emacs/emacs.290508/lisp'
> make[2]: *** [compile] Error 2
> make[2]: Leaving directory `/home/acm/emacs/emacs.290508/lisp'
> make[1]: *** [bootstrap-build] Error 2
> make[1]: Leaving directory `/home/acm/emacs/emacs.290508'
> make: *** [bootstrap] Error 2
>
> Is this my GNU/Linux running out of swap space? Or is it a failure in
> Emacs? I don't think it's good that I automatically assume an Emacs
> fault.
I just built with a fresh checkout on w32. I did not see the problem above.
> Weren't we going to install an automatic build facility which would
> check Emacs still built after commissions? Build failures in the trunk
> seem to be an excessively high drain on productivity and morale at the
> moment.
>
prev parent reply other threads:[~2008-05-29 22:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-29 20:20 Fresh checkout: Seg fault whilst byte-compiling ../lisp/international/mule-cmds.el Alan Mackenzie
2008-05-29 22:03 ` Lennart Borgman (gmail) [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
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=483F283B.3050602@gmail.com \
--to=lennart.borgman@gmail.com \
--cc=acm@muc.de \
--cc=emacs-devel@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).