Re: 2 build issues

From: Junio C Hamano <junkio@cox.net>
Date: Aug 14, 2006, 22:10 UTC
Message-ID: <7vd5b3dl4c.fsf@assigned-by-dhcp.cox.net>
In-Reply-To: <20060814121156.84bc6e34.rdunlap@xenotime.net>

"Randy.Dunlap" <rdunlap@xenotime.net> writes:

Show 9 quoted lines

> xmlto -m callouts.xsl man git-add.xml
> I/O error : Attempt to load network entity http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xsl
> warning: failed to load external entity "http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xsl"
> compilation error: file /tmp/xmlto-xsl.l27115 line 4 element import
> xsl:import : unable to load http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xsl
> make[1]: *** [git-add.1] Error 1
> rm git-add.xml
> make[1]: Leaving directory `/home/rddunlap/builds/git-snapshot-20060814/Documentation'
> make: *** [doc] Error 2

Sorry, I am not docbook expert -- help from the list please? I seem to be using:

                        (home)		(kernel.org)
	asciidoc	7.1.2		7.0.2
        xmlto		0.0.18		0.0.18

Show 13 quoted lines

> make -C templates install
> make[1]: Entering directory `/home/rddunlap/builds/git-snapshot-20060814/templates'
> : no custom templates yet
> install -d -m755 '/usr/local/share/git-core/templates/'
> (cd blt && tar cf - .) | \
> (cd '/usr/local/share/git-core/templates/' && tar xf -)
> tar: This does not look like a tar archive
> tar: Skipping to next header
> tar: Archive contains obsolescent base-64 headers
> tar: Error exit delayed from previous errors
> make[1]: *** [install] Error 2
> make[1]: Leaving directory `/home/rddunlap/builds/git-snapshot-20060814/templates'
> make: *** [install] Error

Hmph. I suspect (cd blt && tar cf - .) is failing silently. When built, "make -C templates" creates templates/blt directory and leaves templates/boilerplates.made file. Do you have them?

Ah, another possibility. Does your "cd" say anything unnecessary even when running scripts, not interactively? For example, do you have CDPATH set and _exported_ to the environment? CDPATH might be a useful shell variable for interactive session, but you never want to export it to affect unsuspecting shell scripts you invoke directly or indirectly.

I see many documents floating on the web that call CDPATH "an environment variable". It is a disease X-<.