all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Emacs Devel <emacs-devel@gnu.org>
Subject: Re: Building Emacs from CVS on windows nt failed
Date: Sun, 17 Oct 2004 14:49:46 -0400	[thread overview]
Message-ID: <87is99mbf3.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <009201c4b474$c50a2940$0200a8c0@sedrcw11488> (Lennart Borgman's message of "Sun, 17 Oct 2004 20:11:27 +0200")

>     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)

`doit' is there to make sure that `make custom-deps' is never considered as
"built".  Admittedly, since the file `custom-deps' doesn't exist any more than
the file `doit', it's not very useful in this case, but it's a more
generic pattern.

IIRC the elisp function `custom-make-dependencies' fails if cus-load.el does
not exist yet.  That's why there is a `cus-load.el' rule which does nothing
more than ensure that the file exists (if it already exists, then the
`cus-load.el' rule is not executed since there is no dependency).

> Does not this always fail the first time, before cus-load.el exists?

It's always worked for me.  Your `touch' program seems odd in that it seems
to refuse to create a file, even though `touch' is often used exactly for
this purpose.


        Stefan

      parent reply	other threads:[~2004-10-17 18:49 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
2004-10-17 18:49   ` Lennart Borgman
2004-10-17 18:49   ` Stefan Monnier [this message]

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=87is99mbf3.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --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 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.