unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Dani Moncayo <dmoncayo@gmail.com>
To: Emacs development discussions <emacs-devel@gnu.org>
Cc: bozhidar@batsov.com
Subject: Bootstrap failure
Date: Mon, 25 Nov 2013 19:54:50 +0100	[thread overview]
Message-ID: <CAH8Pv0hgOt_jq385pf515z8H6bToUC0mm02SEBVFXud02XSMgw@mail.gmail.com> (raw)

make[2]: Entering directory `/home/dani/emacs/build/lisp'
Compiling ../../repo/src/../lisp/emacs-lisp/byte-run.el
../../repo/lisp/emacs-lisp/bytecomp.el:Warning: Unused lexical
variable `interactive-onaly'
In toplevel form:
../../repo/lisp/emacs-lisp/byte-run.el:36:2:Error: Symbol's value as
variable is void: interactive-only
Makefile:248: recipe for target `compile-onefile' failed
make[2]: *** [compile-onefile] Error 1
make[2]: Leaving directory `/home/dani/emacs/build/lisp'
Makefile:788: recipe for target
`../../repo/src/../lisp/emacs-lisp/byte-run.elc' failed
make[1]: *** [../../repo/src/../lisp/emacs-lisp/byte-run.elc] Error 2
make[1]: Leaving directory `/home/dani/emacs/build/src'
Makefile:378: recipe for target `src' failed
make: *** [src] Error 2


-- 
Dani Moncayo



             reply	other threads:[~2013-11-25 18:54 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-25 18:54 Dani Moncayo [this message]
2013-11-25 18:56 ` Bootstrap failure Paul Eggert
2013-11-25 19:18   ` Dani Moncayo
     [not found] <s0d1qc1xxa1.fsf.ref@yahoo.com>
2023-12-05  1:17 ` Po Lu
2023-12-05  3:32   ` Eli Zaretskii
     [not found] <874jmxy7iy.fsf.ref@yahoo.com>
2023-06-24  1:27 ` Po Lu
2023-06-24  2:25   ` Michael Heerdegen
2023-06-24 23:49   ` Michael Heerdegen
  -- strict thread matches above, loose matches on Subject: below --
2010-05-06 23:50 bootstrap failure Angelo Graziosi
2010-05-07  0:14 ` Juanma Barranquero
2010-05-06  9:07 Stephen Berman
2010-05-07 17:52 ` Stefan Monnier
2010-05-07 21:19   ` Stephen Berman
2010-04-20 17:28 Juanma Barranquero
2010-04-20 18:31 ` Stefan Monnier
2010-04-20 19:19   ` Juanma Barranquero
2009-12-08  0:14 Bootstrap failure Angelo Graziosi
2009-11-12 10:44 Romain Francoise
2009-11-12 20:36 ` Sven Joachim
2009-11-14 15:14   ` Chong Yidong
2009-11-14 19:49     ` Bruce Stephens
2009-11-14 20:33       ` Jan Djärv
2009-11-15  1:31         ` Stefan Monnier
2009-11-15  3:48           ` YAMAMOTO Mitsuharu
2009-11-15 12:10             ` Bruce Stephens
2009-11-15 14:56             ` Romain Francoise
2009-11-15  9:30           ` Jan Djärv
2004-12-14  7:30 Dee Zsombor
2004-12-05 13:17 Jérôme Marant
2004-12-05 15:24 ` Luc Teirlinck
2004-12-05 15:28   ` Luc Teirlinck
2004-12-05 15:55   ` Luc Teirlinck
2004-12-05 18:16   ` Jérôme Marant
2004-11-20  0:14 bootstrap failure Luc Teirlinck
2004-11-20  1:24 ` Andreas Schwab
2004-11-20  1:29   ` Luc Teirlinck
2004-11-20 10:38     ` Thien-Thi Nguyen
2004-11-20  3:07   ` Luc Teirlinck

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=CAH8Pv0hgOt_jq385pf515z8H6bToUC0mm02SEBVFXud02XSMgw@mail.gmail.com \
    --to=dmoncayo@gmail.com \
    --cc=bozhidar@batsov.com \
    --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).