From: Mike Frysinger <vapier@gentoo.org>
To: binutils@sourceware.org
Subject: Re: [PATCH] libctf: delete unused libctf_TEXINFOS
Date: Sat, 22 Jan 2022 19:35:57 -0500 [thread overview]
Message-ID: <Yeyi7Ulph7RibR16@vapier> (raw)
In-Reply-To: <20211202044412.24870-1-vapier@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1290 bytes --]
ping ... i'll prob push it in a bit as semi-obvious since the generated
code is not affected by its removal.
-mike
On 01 Dec 2021 23:44, Mike Frysinger via Binutils wrote:
> It's not clear what this was meant for, but it's not used by anything,
> and the info pages still generate fine without it.
> ---
> libctf/Makefile.in | 1 -
> libctf/doc/local.mk | 1 -
> 2 files changed, 2 deletions(-)
>
> diff --git a/libctf/Makefile.in b/libctf/Makefile.in
> index 379f50df44b2..09855ae85a39 100644
> --- a/libctf/Makefile.in
> +++ b/libctf/Makefile.in
> @@ -578,7 +578,6 @@ RUNTESTFLAGS =
> # development.sh is used to determine -Werror default.
> @TCL_TRY_TRUE@CONFIG_STATUS_DEPENDENCIES = $(BFDDIR)/development.sh
> @TCL_TRY_TRUE@EXTRA_DEJAGNU_SITE_CONFIG = development.exp
> -@BUILD_INFO_TRUE@libctf_TEXINFOS = $(info_TEXINFOS)
> @BUILD_INFO_TRUE@AM_MAKEINFOFLAGS = --no-split
> all: config.h
> $(MAKE) $(AM_MAKEFLAGS) all-am
> diff --git a/libctf/doc/local.mk b/libctf/doc/local.mk
> index 7ee2fec78cc7..db319c226766 100644
> --- a/libctf/doc/local.mk
> +++ b/libctf/doc/local.mk
> @@ -18,7 +18,6 @@
> #
>
> info_TEXINFOS += %D%/ctf-spec.texi
> -libctf_TEXINFOS = $(info_TEXINFOS)
>
> AM_MAKEINFOFLAGS = --no-split
>
> --
> 2.33.0
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-01-23 0:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-02 4:44 Mike Frysinger
2022-01-23 0:35 ` Mike Frysinger [this message]
2022-02-10 13:59 ` Nick Alcock
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=Yeyi7Ulph7RibR16@vapier \
--to=vapier@gentoo.org \
--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).