[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: build error
From: |
Andreas Schwab |
Subject: |
Re: build error |
Date: |
Sat, 15 Sep 2007 12:56:50 +0200 |
User-agent: |
Gnus/5.110006 (No Gnus v0.6) Emacs/22.1 (gnu/linux) |
Eli Zaretskii <address@hidden> writes:
>> From: "d.henman" <address@hidden>
>> Date: Fri, 14 Sep 2007 11:36:55 +0900
>> cc:
>>
>> In end of data:
>> bytecomp.el:4255:1:Warning: the function `compilation-forget-errors' is not
>> known to be defined.
>> Wrote /usr/cvs/emacs/lisp/emacs-lisp/bytecomp.elc
>> Compiling /usr/cvs/emacs/lisp/subr.el
>> Fatal error (6)/bin/sh: line 4: 3088 Aborted (core dumped)
>> EMACSLOADPATH=/usr/cvs/emacs/lisp ../src/bootstrap-emacs.exe -batch
>> --no-site-file --multibyte -f batch-byte-compile-if-not-done $el
>> make[2]: *** [compile] Error 1
>>
>> --- end of paste
>>
>> I get from this, that subr.el is the file being compliled when core is
>> dumped, and
>> that this is a compiler fatal error #6 ?
>
> Yes. Fatal error 6 is SIGABRT (see your signal.h header file), as the
> "Aborted" part says. If Emacs was aborted, it means that Emacs exited
> abnormally, most probably via the call to the `abort' function. The
> Emacs sources routinely place the calls to that function where there
> are situations that ``cannot happen'', in order to force a core dump
> that can be debugged to find the reasons.
>
> But it could also be that /bin/sh (presumably the Cygwin port of Bash)
> was the one who aborted,
Definitely not. The printed message clearly points at
bootstrap-emacs.exe as the culprit.
Andreas.
--
Andreas Schwab, SuSE Labs, address@hidden
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."