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

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

[debbugs-tracker] bug#17629: closed (Can't build emacs-24 branch)


From: GNU bug Tracking System
Subject: [debbugs-tracker] bug#17629: closed (Can't build emacs-24 branch)
Date: Thu, 29 May 2014 16:32:03 +0000

Your message dated Thu, 29 May 2014 18:31:14 +0200
with message-id <address@hidden>
and subject line Re: bug#17629: Can't build emacs-24 branch
has caused the debbugs.gnu.org bug report #17629,
regarding Can't build emacs-24 branch
to be marked as done.

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


-- 
17629: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=17629
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: Can't build emacs-24 branch Date: Thu, 29 May 2014 13:07:05 +0200
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)



--- End Message ---
--- Begin Message --- Subject: Re: bug#17629: Can't build emacs-24 branch Date: Thu, 29 May 2014 18:31:14 +0200
On Thu, 29 May 2014 18:04:15 +0300
Eli Zaretskii <address@hidden> wrote:

> > From: Jorgen Schaefer <address@hidden>
> > Date: Thu, 29 May 2014 13:07:05 +0200
> > 
> > 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:
> 
> This doesn't seem to be a clean tree:

Indeed, this was a simple user error. Sorry for the noise.

> Did you switch to the emacs-24 branch in the same git repository, and
> then typed the command above?  If so, either "make bootstrap" or clone
> a separate repository, switch to emacs-24 there, and then your
> commands should work.

I did a git reset --hard and make distclean, but not a make bootstrap.
git st told me the repo was clean, but that obviously does not check
files in .gitignore. I should have used git clean. Meh.

Thanks for the quick response.

Regards,
Jorgen


--- End Message ---

reply via email to

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