unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
* Fresh checkout: Seg fault whilst byte-compiling ../lisp/international/mule-cmds.el
@ 2008-05-29 20:20 Alan Mackenzie
  2008-05-29 22:03 ` Lennart Borgman (gmail)
  0 siblings, 1 reply; 2+ messages in thread
From: Alan Mackenzie @ 2008-05-29 20:20 UTC (permalink / raw)
  To: emacs-devel

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.

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.

-- 
Alan Mackenzie (Nuremberg, Germany)




^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: Fresh checkout: Seg fault whilst byte-compiling ../lisp/international/mule-cmds.el
  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)
  0 siblings, 0 replies; 2+ messages in thread
From: Lennart Borgman (gmail) @ 2008-05-29 22:03 UTC (permalink / raw)
  To: Alan Mackenzie; +Cc: emacs-devel

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.
> 




^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2008-05-29 22:03 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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)

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).