From: Eli Zaretskii <eliz@gnu.org>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Make "all" depend on "info"
Date: Sun, 07 Apr 2019 02:34:00 -0000 [thread overview]
Message-ID: <835zrqa6h0.fsf@gnu.org> (raw)
In-Reply-To: <20190406204834.23321-1-tom@tromey.com> (message from Tom Tromey on Sat, 6 Apr 2019 14:48:34 -0600)
> From: Tom Tromey <tom@tromey.com>
> Cc: Tom Tromey <tom@tromey.com>
> Date: Sat, 6 Apr 2019 14:48:34 -0600
>
> This patch changes doc/Makefile.in so that the info pages are built by
> "make all". As a point of reference, Automake has essentially always
> worked this way. According to the Automake manual (I didn't
> double-check) this is required by the GNU coding standards.
>
> The first time I sent this patch, I mentioned that I wanted to look
> into some existing bugs in bugzilla about missing "makeinfo".
> However, today I tried and I discovered that BFD requires makeinfo,
> and builds its info file as part of "all". So, I think this change
> doesn't worsen the situation for users in any way, and can simply go
> in.
Fine with me, but did you verify the prerequisites won't cause the
manual rebuilt when not necessary? IOW, does INFO_DEPS include
anything except the Texinfo sources?
Thanks.
next prev parent reply other threads:[~2019-04-07 2:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-06 20:48 Tom Tromey
2019-04-07 2:34 ` Eli Zaretskii [this message]
2019-04-07 23:04 ` Tom Tromey
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=835zrqa6h0.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.com \
/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