From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: "ZSH workers mailing list" <zsh-workers@sunsite.auc.dk>
Subject: PATCH: Not quite Re: info is rebuilt every time
Date: Wed, 5 Apr 2000 08:32:26 +0000 [thread overview]
Message-ID: <1000405083226.ZM14407@candle.brasslantern.com> (raw)
In-Reply-To: <003301bf9ecb$f1397ed0$21c9ca95@mow.siemens.ru>
On Apr 5, 10:55am, Andrej Borsenkow wrote:
} Subject: info is rebuilt every time
}
} Every time I run make info gets rebuilt. It is espicially annoying now
} with CVS updates. Today's update did not touch yo files for all I can
} tell - the newest file is from 2nd April.
That's a little odd ... zsh.info is *never* rebuilt for me, unless I
explicitly "make install.info" or "(cd Doc; make zsh.info)".
On the other hand, stamp-h.in always gets rebuilt for me, because I use
a build dir separate from the source dir and the rules for the stamp-h.in
target build $(sdir)/stamp-h.in rather than stamp-h.in, so ./stamp-h.in
never gets any newer.
In the interest of trying to fix your bug (the patch below is for mine),
let me ask: Do you have yodl? If so, is zsh.texi getting rebuilt, too,
or is it just that makeinfo always runs?
If you have GNU make, "make -n -d -s --no-print-directory >& make.out"
and then edit make.out and search for zsh.info -- you should be able to
find what it believes the unsatisfied dependency to be.
(I'll check the following in to sourceforge as soon as I know the article
number.)
Index: Makefile.in
===================================================================
@@ -138,19 +138,20 @@
config: config.h
-config.status: configure
+config.status: $(sdir)/configure
./config.status --recheck
-configure: configure.in aclocal.m4 aczsh.m4
+$(sdir)/configure: $(sdir)/configure.in $(sdir)/aclocal.m4 $(sdir)/aczsh.m4
cd $(sdir) && autoconf
config.h: stamp-h
-stamp-h: config.h.in config.status
+stamp-h: $(sdir)/config.h.in config.status
cd $(dir_top) && \
CONFIG_FILES= CONFIG_HEADERS=$(subdir)/config.h ./config.status
-config.h.in: stamp-h.in
-stamp-h.in: configure.in acconfig.h aclocal.m4 aczsh.m4
+$(sdir)/config.h.in: $(sdir)/stamp-h.in
+$(sdir)/stamp-h.in: $(sdir)/configure.in $(sdir)/acconfig.h \
+ $(sdir)/aclocal.m4 $(sdir)/aczsh.m4
cd $(sdir) && autoheader
echo > $(sdir)/stamp-h.in
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
next prev parent reply other threads:[~2000-04-05 8:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-05 6:55 Andrej Borsenkow
2000-04-05 8:32 ` Bart Schaefer [this message]
2000-04-05 8:42 ` PATCH: Not quite " Andrej Borsenkow
2000-04-05 13:01 ` Zefram
2000-04-05 14:51 ` Bart Schaefer
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=1000405083226.ZM14407@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--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).