emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[debbugs-tracker] bug#11649: closed (Some compilation woes)


From: GNU bug Tracking System
Subject: [debbugs-tracker] bug#11649: closed (Some compilation woes)
Date: Fri, 15 Jun 2012 19:27:02 +0000

Your message dated Fri, 15 Jun 2012 21:22:33 +0200
with message-id <address@hidden>
and subject line Re: bug#11649: 24.1.50; Some compilation woes
has caused the debbugs.gnu.org bug report #11649,
regarding Some compilation woes
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
11649: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=11649
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: Some compilation woes Date: Fri, 8 Jun 2012 15:19:27 +0200
Package: emacs
Version: 24.1.50


1) Bootstrapping now generates a few "lisp nesting exceeds
max-lisp-eval-depth" errors:

In toplevel form:
progmodes/make-mode.el:324:1:Error: Lisp nesting exceeds `max-lisp-eval-depth'

In toplevel form:
textmodes/rst.el:271:1:Error: Lisp nesting exceeds `max-lisp-eval-depth'

In toplevel form:
cedet/semantic/bovine/c-by.el:183:1:Error: Lisp nesting exceeds
`max-lisp-eval-depth'


2) Byte-compilation generates lots of new "function X might not be
defined at runtime". AFAICS, they are generated for functions used
before they are defined (with defun).

3) Byte-compilation seems quite fragile. After a successful bootstrap,
touch'ing every *.el in lisp/** and doing

  cd lisp
  make recompile

produces quite a few errors:

  Generating autoloads for ibuf-macs.el...
  Autoload cookie error in ibuf-macs.el:129 (wrong-type-argument integerp nil)
  Autoload cookie error in ibuf-macs.el:160 (wrong-type-argument integerp nil)
  Autoload cookie error in ibuf-macs.el:264 (wrong-type-argument integerp nil)
  Autoload cookie error in ibuf-macs.el:299 (wrong-type-argument integerp nil)
  Generating autoloads for ibuf-macs.el...done


  In toplevel form:
  textmodes/rst.el:120:1:Error: Invalid byte code in
c:/emacs/trunk/lisp/emacs-lisp/cl-macs.elc
  Checking c:/emacs/trunk/lisp/url...
  Checking c:/emacs/trunk/lisp/vc...
  Compiling c:emacs/repo/lisp/vc/pcvs.el...
  Compiler-macro error: (error "Invalid byte code in
c:/emacs/trunk/lisp/emacs-lisp/cl-macs.elc")
  Compiler-macro error: (error "Invalid byte code in
c:/emacs/trunk/lisp/emacs-lisp/cl-macs.elc")
  etc

    Juanma



--- End Message ---
--- Begin Message --- Subject: Re: bug#11649: 24.1.50; Some compilation woes Date: Fri, 15 Jun 2012 21:22:33 +0200
On Fri, Jun 15, 2012 at 8:27 PM, Eli Zaretskii <address@hidden> wrote:

> It does the right thing, but should not be used in certain situations.
> I don't think you can "fix" that, except if you remove that target
> altogether.

OK, closing then.

    Juanma


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]