unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Jorgen Schaefer <forcer@forcix.cx>
To: 17629@debbugs.gnu.org
Subject: bug#17629: Can't build emacs-24 branch
Date: Thu, 29 May 2014 13:07:05 +0200	[thread overview]
Message-ID: <87bnugsv1i.fsf@loki.jorgenschaefer.de> (raw)

Building the current emacs-24 branch fails for me.

Latest commit (git ref, sorry, no bzr here):

3302b06 Do not mention individual ns options in the manual

In a fresh checkout and with a clean tree:

$ ./autogen.sh && ./configure --without-x && make clean && make

[...]

make[2]: Leaving directory `/home/forcer/Programs/Emacs/trunk/lisp'
if test "no" = "yes"; then \
          rm -f bootstrap-emacs; \
          ln temacs bootstrap-emacs; \
        else \
          ./temacs --batch --load loadup bootstrap || exit 1; \
          test "X" = X ||  -zex emacs; \
          mv -f emacs bootstrap-emacs; \
        fi
Loading loadup.el (source)...
Using load-path (/home/forcer/Programs/Emacs/trunk/lisp /home/forcer/Programs/Emacs/trunk/lisp/emacs-lisp /home/forcer/Programs/Emacs/trunk/lisp/language /home/forcer/Programs/Emacs/trunk/lisp/international /home/forcer/Programs/Emacs/trunk/lisp/textmodes /home/forcer/Programs/Emacs/trunk/lisp/vc)
Loading emacs-lisp/byte-run (compiled; note, source file is newer)...
Loading emacs-lisp/backquote...
Loading subr (compiled; note, source file is newer)...
Loading version...
Loading widget...
Loading custom...
Loading emacs-lisp/map-ynp...
Loading international/mule...
Loading international/mule-conf...
Loading env...
Loading format...
Loading bindings...
Loading cus-start (compiled; note, source file is newer)...
Note, built-in variable `report-emacs-bug-address' not bound
Loading window (compiled; note, source file is newer)...
Loading files (compiled; note, source file is newer)...
Loading emacs-lisp/macroexp (compiled; note, source file is newer)...
Loading cus-face (compiled; note, source file is newer)...
Loading faces (compiled; note, source file is newer)...
Loading button...
Loading startup (compiled; note, source file is newer)...
Loading /home/forcer/Programs/Emacs/trunk/lisp/loaddefs.el (source)...
Wrong number of arguments: (2 . 2), 1
make[1]: *** [bootstrap-emacs] Error 1
make[1]: Leaving directory `/home/forcer/Programs/Emacs/trunk/src'
make: *** [src] Error 2           


x86_64-unknown-linux-gnu
System Description:	Debian GNU/Linux 7.5 (wheezy)





             reply	other threads:[~2014-05-29 11:07 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-29 11:07 Jorgen Schaefer [this message]
2014-05-29 14:47 ` bug#17629: Can't build emacs-24 branch Paul Eggert
2014-05-29 15:04 ` Eli Zaretskii
2014-05-29 16:06   ` Glenn Morris
2014-05-29 16:31   ` Jorgen Schaefer
2014-05-29 16:56     ` Glenn Morris
2014-05-29 17:28       ` Stefan Monnier
2014-05-29 19:12         ` Glenn Morris
2014-05-29 20:33           ` Stefan Monnier

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=87bnugsv1i.fsf@loki.jorgenschaefer.de \
    --to=forcer@forcix.cx \
    --cc=17629@debbugs.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).