From: Adam Spiers <adam@spiers.net>
To: zsh workers mailing list <zsh-workers@sunsite.auc.dk>
Subject: Re: duplicate targets in Makefile rule
Date: Thu, 10 Feb 2000 13:37:36 +0000 [thread overview]
Message-ID: <20000210133736.A12687@thelonious.new.ox.ac.uk> (raw)
In-Reply-To: <E12IqMG-0003bS-00@crucigera.fysh.org>
Zefram (zefram@fysh.org) wrote:
> Adam Spiers wrote:
> >When is sdir not `.'?
>
> When you're compiling in a build tree separate from the source tree.
I see ... so how can we stop make from complaining when sdir is `.' ?
If we're compiling in a separate build tree then presumably we don't
need a rule for the source tree version of zsh.texi, so can we just
get rid of the zsh.texi target and leave the $(dir)/zsh.texi one? If
we can, the patch is below. However noone else seems to have
encountered a problem with this (and neither did I before Christmas),
so it's more likely I've done something wrong. Any ideas what?
Index: Doc/Makefile.in
===================================================================
RCS file: /projects/zsh/zsh/Doc/Makefile.in,v
retrieving revision 1.1.1.60
diff -u -r1.1.1.60 Makefile.in
--- Doc/Makefile.in 2000/02/07 01:59:21 1.1.1.60
+++ Doc/Makefile.in 2000/02/10 13:33:29
@@ -82,7 +82,7 @@
zsh.dvi: $(sdir)/zsh.texi
$(TEXI2DVI) $(sdir)/zsh.texi
-zsh.texi $(sdir)/zsh.texi:
+$(sdir)/zsh.texi:
case $@ in \
*/*) target=$@ ;; \
*) target=$(sdir)/$@ ;; \
next prev parent reply other threads:[~2000-02-10 13:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-02-09 23:58 Adam Spiers
2000-02-10 9:57 ` Zefram
2000-02-10 13:37 ` Adam Spiers [this message]
2000-02-10 13:54 ` Andrej Borsenkow
2000-02-10 14:23 ` Adam Spiers
2000-02-10 14:31 ` Zefram
2000-02-10 15:36 ` PATCH: " Adam Spiers
2000-02-10 15:43 ` Zefram
2000-02-10 17:03 ` Adam Spiers
2000-02-10 17:11 ` Zefram
2000-02-21 2:12 ` Adam Spiers
2000-02-21 10:07 ` Zefram
2000-02-21 10:39 ` Adam Spiers
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=20000210133736.A12687@thelonious.new.ox.ac.uk \
--to=adam@spiers.net \
--cc=zsh-workers@sunsite.auc.dk \
/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.vuxu.org/mirror/zsh/
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 NNTP newsgroup(s).