Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Alan Modra <amodra@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: gdb-patches@sourceware.org, binutils@sourceware.org
Subject: Re: [PATCH][PING²] PR external/{16327,16328}: Remove etc/configure.texi and etc/standards.texi
Date: Fri, 27 Jun 2014 02:46:00 -0000	[thread overview]
Message-ID: <20140627024638.GC23042@bubble.grove.modra.org> (raw)
In-Reply-To: <87ionnsua4.fsf@gnu.org>

On Thu, Jun 26, 2014 at 02:57:23PM +0200, Ludovic Courtès wrote:
> etc/ChangeLog
> 2014-06-26  Ludovic Courtès  <ludo@gnu.org>
> 
> 	PR external/16327
> 	PR external/16328
> 	* Makefile.in (MAKEINFO, TEXI2DVI, TEXI2PDF, TEXI2HTML, DVIPS,
> 	TEXIDIR, INFOFILES, DVIFILES, PDFFILES, HTMLFILES): Remove.
> 	(all): Remove dependency on 'info'.
> 	(install): Remove dependency on 'install-info'.
> 	(standards.info, standards.html, standards.dvi, standards.ps)
> 	standards.pdf, configure.info, configure.dvi, configure.ps,
> 	configure.pdf, configure.pdf): Remove.
> 	(info, install-info, html, install-html, dvi, pdf, install-pdf)
> 	clean, maintainer-clean, realclean): Remove body.
> 	* etc/configbuild.ein, etc/configbuild.fig, etc/configbuild.jin,
> 	etc/configbuild.tin, etc/configdev.ein, etc/configdev.fig,
> 	etc/configdev.jin, etc/configdev.tin, etc/configure.texi,
> 	etc/fdl.texi, etc/gnu-oids.texi, etc/make-stds.texi,
> 	etc/standards.texi: Remove.

I think we've had enough time for anyone to register disagreement with
this patch, so OK to apply.

I notice this leaves us with a Makefile that does nothing.  As a
followup you might like to delete etc/configure* and etc/Makefile.in
and remove the line "host_modules= { module= etc; };" in the top level
Makefile.def.  I also see this in Makefile.tpl
dist:
	@echo "Building a full distribution of this tree isn't done"
	@echo "via 'make dist'.  Check out the etc/ subdirectory" 
Seems like that should be removed too.

The top level Makefile.def and Makefile.tpl changes (and regen of
Makefile.in) would need to be applied to mainline gcc too.

-- 
Alan Modra
Australia Development Lab, IBM


  reply	other threads:[~2014-06-27  2:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-05 15:51 [PATCH] " Ludovic Courtès
2014-05-13 16:35 ` [PING] " Ludovic Courtès
2014-05-13 17:29   ` Pedro Alves
2014-05-14 10:34     ` Ludovic Courtès
2014-06-26 12:57 ` [PATCH][PING²] " Ludovic Courtès
2014-06-27  2:46   ` Alan Modra [this message]
2014-06-27  9:43     ` Ludovic Courtès
2014-07-07 14:22       ` Joel Brobecker
2014-07-07 15:17         ` Ludovic Courtès
2014-07-07 15:22           ` Joel Brobecker

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=20140627024638.GC23042@bubble.grove.modra.org \
    --to=amodra@gmail.com \
    --cc=binutils@sourceware.org \
    --cc=gdb-patches@sourceware.org \
    --cc=ludo@gnu.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