From: Nick Clifton <nickc@redhat.com>
To: Ulf Samuelsson <binutils@emagii.com>, Binutils <binutils@sourceware.org>
Subject: Re: How create output from ldint.texi ?
Date: Fri, 17 Feb 2023 11:24:49 +0000 [thread overview]
Message-ID: <654411b8-dc10-97b4-f002-22d1ea4e2ae2@redhat.com> (raw)
In-Reply-To: <feedd273-5b3c-176a-d3d8-90287490fed1@emagii.com>
Hi Ulf,
> How is it possible to create a PDF file from this file.
By running a command something like this:
TEXINPUTS="/work/sources/binutils/upstream/current/ld/../texinfo:$TEXINPUTS" \
MAKEINFO='/bin/sh /work/sources/binutils/upstream/current/missing makeinfo -I /work/sources/binutils/upstream/current/ld -I
/work/sources/binutils/upstream/current/ld/../bfd/doc -I ../bfd/doc -I /work/sources/binutils/upstream/current/ld/../libiberty --no-split -I
/work/sources/binutils/upstream/current/ld' \
texi2dvi -I /work/sources/binutils/upstream/current/ld -I /work/sources/binutils/upstream/current/ld/../bfd/doc -I ../bfd/doc -I
/work/sources/binutils/upstream/current/ld/../libiberty --pdf --batch --build-dir=ldint.t2p -o ldint.pdf /work/sources/binutils/upstream/current/ld/ldint.texi
I basically captured the output from running "make ld.pdf"
and tweaked it so that it would create the ldint.pdf document
instead.
> It seems to be disabled in the ld/Makefile.am
>
> noinst_TEXINFOS = ldint.texi
>
> No ldint.info to be found in the tree after the build
This appears to be a bug in the automake program. The noinst_
prefix is meant to stop installation, but not building...
Cheers
Nick
prev parent reply other threads:[~2023-02-17 11:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-16 11:14 Ulf Samuelsson
2023-02-17 11:24 ` Nick Clifton [this message]
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=654411b8-dc10-97b4-f002-22d1ea4e2ae2@redhat.com \
--to=nickc@redhat.com \
--cc=binutils@emagii.com \
--cc=binutils@sourceware.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).