[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Building Emacs from CVS on windows nt failed
From: |
Lennart Borgman |
Subject: |
Re: Building Emacs from CVS on windows nt failed |
Date: |
Sun, 17 Oct 2004 20:11:27 +0200 |
----- Original Message -----
From: "Lennart Borgman" <address@hidden>
To: "Emacs Devel" <address@hidden>
Sent: Sunday, October 17, 2004 3:42 PM
Subject: Building Emacs from CVS on windows nt failed
: I took some time to download the CVS version and started building it. It
: fails in make boostrap with the following:
:
: Wrote c:/emacscvs/emacs/lisp/finder-inf.el
: touch cus-load.el
: Can't touch cus-load.el - No such file or directory
: make[1]: *** [cus-load.el] Error 1
: make[1]: Leaving directory `/c/emacscvs/emacs/lisp'
: make: *** [bootstrap-gmake] Error 2
Jason Rumney pointed out that cus-load.el is an autogenerated file (which I
saw too late). I can't really understand the makerules for this:
doit:
cus-load.el:
touch $@
custom-deps: cus-load.el doit
@echo Directories: $(WINS)
-$(emacs) -l cus-dep --eval $(ARGQUOTE)(setq find-file-hooks
nil)$(ARGQUOTE) -f custom-make-dependencies $(lisp) $(WINS)
Why do custom-deps have "prerequisites"? Could not these just be removed?
(May the "touch $@" should be replaced with a command "touch cus-load.el" at
the bottom - if it is needed?)
Does the prerequisites have something to do with different make programs?
Does not this always fail the first time, before cus-load.el exists? (I have
read that many people say that make bootstrap often fails, it that problem
connected with this?)
- Lennart