[PATCH] Fix building release tar ball without makeinfo

Bernd Edlinger bernd.edlinger@hotmail.de
Sun Jan 11 23:11:00 GMT 2015


Hi,

I noticed that it is not possible to build the binutils-2.25 release tar ball without makeinfo.

This configuration fails ../binutils-2.25/configure;
While ./configure may work but is not the recommended way.

The problem seems to start with this commit:

commit 19e1c431f72007f8a7a6a8e8b2511c74f3e8a000
Author: Alan Modra <amodra@gmail.com>
Date:   Wed Apr 9 13:23:41 2014 +0930

    Add a time-stamp for chew
    
    One last time-stamp.  Now none of the doc rules using move-if-change
    will run unnecessarily.

I've attached a patch for this.  The problem is that the *.stamp rules run at least once, and create
new *.texi in the build folder, and these new *.texi are newer than the bfd.info.  It does not help
that there are identical versions in the source tree.  The patch tries to keep the time stamp from the
source tree, if the *.texi do not change.

To install the patch on the tar ball, you must use patch -p1 -T because the time stamp of the pre-computed
texi files must not be older than the bfd/doc/Makefile.in,
I tried to make sure that the patch does also work with in-tree builds, and in maintainer-mode (without *.texi).

OK for trunk?


Thanks
Bernd.
 		 	   		  
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: changelog-binutils-doc.txt
URL: <https://sourceware.org/pipermail/binutils/attachments/20150111/84ec94c1/attachment.txt>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: changelog-binutils-doc.txt
URL: <https://sourceware.org/pipermail/binutils/attachments/20150111/84ec94c1/attachment-0001.txt>


More information about the Binutils mailing list