From: "Lennart Borgman" <lennart.borgman.073@student.lu.se>
Subject: Re: Building Emacs from CVS on windows nt failed
Date: Sun, 17 Oct 2004 20:11:27 +0200 [thread overview]
Message-ID: <009201c4b474$c50a2940$0200a8c0@sedrcw11488> (raw)
In-Reply-To: 004d01c4b44f$3cf4d1b0$0200a8c0@sedrcw11488
----- Original Message -----
From: "Lennart Borgman" <lennart.borgman.073@student.lu.se>
To: "Emacs Devel" <emacs-devel@gnu.org>
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
next prev parent reply other threads:[~2004-10-17 18:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-17 13:42 Building Emacs from CVS on windows nt failed Lennart Borgman
2004-10-17 16:17 ` Jason Rumney
2004-10-17 18:11 ` Lennart Borgman [this message]
2004-10-17 18:49 ` Lennart Borgman
2004-10-17 18:49 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='009201c4b474$c50a2940$0200a8c0@sedrcw11488' \
--to=lennart.borgman.073@student.lu.se \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.