|
From: | Doug Stewart |
Subject: | Re: docs not building |
Date: | Wed, 8 Jul 2015 09:29:55 -0400 |
On Wed, Jul 08, 2015 at 08:04:26 -0400, John W. Eaton wrote:
> On 07/08/2015 12:06 AM, Mike Miller wrote:
> >Fails for me, the attached change works better for me
>
> How does it fail? With or without my change? Can you show what happens
> with "make V=1 ..." and say whether that was with my patch or not?
Yes, with your change. I am on 9e361ecea878 with no changes now, I
configure with ../configure so srcdir=.. for reference. The command that
fails is
cd doc/refcard && \
TEXINPUTS="../doc/refcard::../doc/interpreter::./doc/interpreter::../doc/interpreter::./doc/interpreter::../doc/interpreter::./doc/interpreter:::::" \
tex refcard-a4.tex
This is TeX, Version 3.14159265 (TeX Live 2015/Debian) (preloaded format=tex)
! I can't find file `refcard-a4.tex'.
<*> refcard-a4.tex
(Press Enter to retry, or Control-D to exit)
Please type another input file name:
which looks accurate to me (that it can't find the input file).
> > Is the TeX
> >output-directory option portable enough?
> >
>
> I don't know, so it seems better to me to use cd and fix the input file
> name. Does it also work for you with $(<F) instead of $< ?
I think in general once the current directory is changed you lose all
assumptions about the relationship between the source directory and
build directory so that's a downside to cd'ing.
I can also get your change to work for me by changing:
-$(AM_V_TEX)cd $(@D) && \
- TEXINPUTS="$(srcdir)/doc/refcard:$(TEXINPUTS):" \
+ TEXINPUTS="$(abs_srcdir)/doc/refcard:$(TEXINPUTS):" \
$(TEX) $(<F) $(AM_V_texidevnull)
so maybe that's a better workaround.
We might want to do the same to the definition of TEXINPUTS elsewhere if
the current directory is going to be changing, the other relative
directories in that search path also become invalid.
--
mike
[Prev in Thread] | Current Thread | [Next in Thread] |