On Sat, 28 Mar 2020, Sven Schreiber wrote:
Am 28.03.2020 um 08:45 schrieb Sven Schreiber:
> Am 28.03.2020 um 02:39 schrieb Allin Cottrell:
>> On Fri, 27 Mar 2020, Sven Schreiber wrote:
>
>>> Sorry, still stuck here:
>>>
>>> make[4]: Verzeichnis „/home/fantomas/src/build/doc/commands“ wird
>>> verlassen
>>> LANG=en_US date "+%B, %Y" > date.tex
>>> pdflatex gretl-ref.tex
>>> make[3]: pdflatex: No such file or directory
>>> make[3]: *** [Makefile:144: gretl-ref.pdf] Fehler 127
>>> make[3]: Verzeichnis „/home/fantomas/src/build/doc/tex“ wird verlassen
>>> make[2]: *** [Makefile:277: ../tex/gretl-ref.bbl] Fehler 2
>>> make[2]: Verzeichnis „/home/fantomas/src/build/doc/commands“ wird
>>> verlassen
>>> make[1]: *** [Makefile:60: help] Fehler 2
>>> make[1]: Verzeichnis „/home/fantomas/src/build/share“ wird verlassen
>>> make: *** [Makefile:69: share] Fehler 2
>>
>> Oh god, this is so fiddly! Another Makefile.in revision is now in git.
>> (I presume you've got this OK, but when any Makefile.in is modified, the
>> configure script must be re-run to get the Makefiles updated.)
>
> Right. Last time I even deleted all non-git versioned files explicitly
> to be on the safe side.
This time I "only" deleted the build directory and re-ran the setup.sh
which also re-configures.
> But now one more round of testing the latest git changes.
Unfortunately, exactly the same message as above.
I've had another go at the Makefiles, which might help, but if it
still doesn't work I'll need some more information to identify the
error.
If the pdflatex executable itself is found OK there should be some
message from it. If the tex file on the command line (say,
"foo.tex") is missing there should be something like:
! I can't find file `foo.tex'.
If foo.tex is present but some included file is not found, there
should be a log file foo.log which identifies the error.
Allin