From: Tobias Burnus <tobias@codesourcery.com>
To: "H.J. Lu" <hjl.tools@gmail.com>, Mike Frysinger <vapier@gentoo.org>
Cc: Binutils <binutils@sourceware.org>
Subject: Re: [PATCH] bfd: Pass -Idoc to $(MAKEINFOHTML)
Date: Mon, 24 Jan 2022 17:52:06 +0100 [thread overview]
Message-ID: <e95de882-450c-7834-7c74-efaaa3a91a9d@codesourcery.com> (raw)
In-Reply-To: <CAMe9rOqaaKJqnbnB1c3YG+K4Zow82kF_EfawsFrhjXYRy5m9Ag@mail.gmail.com>
Hi H.J., hi Mike,
On 24.01.22 16:42, H.J. Lu wrote:
> Try this.
That does not fail - but it creates an empty <body> HTML file.
I think it is the same reason as the one why creating the PDF
file fails hard.
Namely, for the 'doc/bfd.pdf' (or 'install-pdf') is does as first
step:
touch doc/bfd.texi
which creates an empty file. The 'test -f doc/bfd.texi' then succeeds
and uses that empty file - instead of $(src)/bfd/doc/bfd.texi :-(
On the Makefile level, that's due to the following (Makefile{,.in} + bfd/doc/local.mk):
# Avoid the %.stamp generating a builddir/bfd.texi that overrides the srcdir/.
doc/bfd.texi doc/bfd.stamp: doc/$(am__dirstamp) ; $(AM_V_at)touch $@
And the the 'touch' at the end *is* run for 'doc/bfd.texi' via (Makefile{,.in}):
(Actually, it does the opposite to what comment states: It does create that file!)
I think that target is invoked via:
doc/bfd.pdf: doc/bfd.texi $(doc_bfd_TEXINFOS) doc/$(am__dirstamp)
.... $(TEXI2PDF) ...
due to the bfd.texi dependency.
The "make doc/bfd.pdf" shows/fails with:
touch doc/bfd.texi
TEXINPUTS="$(build)/bfd:$TEXINPUTS" \
MAKEINFO='makeinfo --split-size=5000000 --split-size=5000000 --no-split -I doc -I $(src)/bfd/doc' \
texi2dvi --pdf --batch --build-dir=doc/bfd.t2p -o doc/bfd.pdf \
`test -f 'doc/bfd.texi' || echo '$(src)/bfd/'`doc/bfd.texi
This is pdfTeX, Version 3.14159265-2.6-1.40.20 (TeX Live 2019/Debian) (preloaded format=pdfetex)
restricted \write18 enabled.
entering extended mode
(../../../../.././doc/bfd.texi)
! Emergency stop.
<*> ...opmode \input ../../../../.././doc/bfd.texi
! ==> Fatal error occurred, no output PDF file produced!
Transcript written on bfd.log.
/usr/bin/texi2dvi: pdfetex exited with bad status, quitting.
make[3]: *** [Makefile:1807: doc/bfd.pdf] Error 1
The .log file is in '$(build)/bfd/doc/bfd.t2p/doc!bfd.t2d/pdf/build' and it contains:
**\nonstopmode \input ../../../../.././doc/bfd.texi
(../../../../.././doc/bfd.texi)
! Emergency stop.
<*> ...opmode \input ../../../../.././doc/bfd.texi
which is the empty 'touched' $(build)/bfd/bfd.texi.
Tobias
-----------------
Siemens Electronic Design Automation GmbH; Anschrift: Arnulfstraße 201, 80634 München; Gesellschaft mit beschränkter Haftung; Geschäftsführer: Thomas Heurung, Frank Thürauf; Sitz der Gesellschaft: München; Registergericht München, HRB 106955
next prev parent reply other threads:[~2022-01-24 16:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-24 9:05 [Regression] Build fail: 'doc/bfd/index.html' ($(build)/bfd/bfd.texi - no such file) – probably due to: "bfd: Properly install library and header files" Tobias Burnus
2022-01-24 13:21 ` H.J. Lu
2022-01-24 15:01 ` Tobias Burnus
2022-01-24 15:42 ` [PATCH] bfd: Pass -Idoc to $(MAKEINFOHTML) H.J. Lu
2022-01-24 16:52 ` Tobias Burnus [this message]
2022-01-24 17:48 ` [PATCH v2] bfd: Update doc/local.mk H.J. Lu
2022-01-24 18:38 ` Tobias Burnus
2022-01-24 18:53 ` [PATCH v3] " H.J. Lu
2022-01-24 20:35 ` Tobias Burnus
2022-01-24 20:56 ` H.J. Lu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e95de882-450c-7834-7c74-efaaa3a91a9d@codesourcery.com \
--to=tobias@codesourcery.com \
--cc=binutils@sourceware.org \
--cc=hjl.tools@gmail.com \
--cc=vapier@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).