info is rebuilt every time

info is rebuilt every time

[Andrej Borsenkow]

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.

-andrej

Have a nice DOS!
B >>

PATCH: Not quite Re: info is rebuilt every time

[Bart Schaefer]

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

RE: PATCH: Not quite Re: info is rebuilt every time

[Andrej Borsenkow]

>
> That's a little odd ... zsh.info is *never* rebuilt for me, unless I
> explicitly "make install.info" or "(cd Doc; make zsh.info)".
>
>
> 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?
>


Sorry, I meant zsh.texi of course, not info files.

Well, "every time" is probably not quite correct. I did run gmake now
and nothing happened. I'll try to script next time after CVS update to
see what happens.

-andrej

Re: PATCH: Not quite Re: info is rebuilt every time

[Zefram]

Bart Schaefer wrote:
>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 this case, ./stamp-h.in shouldn't exist.

-zefram

Re: PATCH: Not quite Re: info is rebuilt every time

[Bart Schaefer]

On Apr 5,  2:01pm, Zefram wrote:
} Subject: Re: PATCH: Not quite Re: info is rebuilt every time
}
} Bart Schaefer wrote:
} >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 this case, ./stamp-h.in shouldn't exist.

It exists only because I'm still using the same build tree that I was back
in December, and some previous version of the makefiles created it then.
"make clean" of course doesn't remove it because it doesn't know that it's
there ...

-- 
Bart Schaefer                                 Brass Lantern Enterprises
http://www.well.com/user/barts              http://www.brasslantern.com