public inbox for gdb-cvs@sourceware.org
help / color / mirror / Atom feed
From: Michael Frysinger <vapier@sourceware.org>
To: bfd-cvs@sourceware.org, gdb-cvs@sourceware.org
Subject: [binutils-gdb] libctf: delete unused libctf_TEXINFOS
Date: Fri, 11 Feb 2022 09:21:14 +0000 (GMT)	[thread overview]
Message-ID: <20220211092114.66B583858D1E@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=7c1aa0090f673e29e0b54eae9975b2c1b72a49d2

commit 7c1aa0090f673e29e0b54eae9975b2c1b72a49d2
Author: Mike Frysinger <vapier@gentoo.org>
Date:   Wed Dec 1 23:43:29 2021 -0500

    libctf: delete unused libctf_TEXINFOS
    
    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.

Diff:
---
 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 3b5ab73324e..1984f50867a 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 cc7d990ebd0..93177971a92 100644
--- a/libctf/doc/local.mk
+++ b/libctf/doc/local.mk
@@ -20,7 +20,6 @@
 if BUILD_INFO
 
 info_TEXINFOS += %D%/ctf-spec.texi
-libctf_TEXINFOS = $(info_TEXINFOS)
 
 AM_MAKEINFOFLAGS = --no-split


                 reply	other threads:[~2022-02-11  9:21 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20220211092114.66B583858D1E@sourceware.org \
    --to=vapier@sourceware.org \
    --cc=bfd-cvs@sourceware.org \
    --cc=gdb-cvs@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).