public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Mike Stump <mikestump@comcast.net>
To: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: libiberty TAGS
Date: Thu, 18 Jun 2015 20:35:00 -0000	[thread overview]
Message-ID: <17242213-EF29-4BDE-929B-AB383C8AA9B2@comcast.net> (raw)

I was making tags in libiberty and noticed it just didn’t work.  :-(

This is one easy way to fix it.

Ok?

diff --git a/libiberty/Makefile.in b/libiberty/Makefile.in
index f06cc69..876fab2 100644
--- a/libiberty/Makefile.in
+++ b/libiberty/Makefile.in
@@ -409,8 +409,9 @@ stamp-noasandir:
 
 etags tags: TAGS etags-subdir
 
+VPATH = @srcdir@
 TAGS: $(CFILES)
-       etags `for i in $(CFILES); do echo $(srcdir)/$$i ; done`
+       cd $(srcdir) && etags `for i in $(CFILES); do echo $(srcdir)/$$i ; done`
 
 # The standalone demangler (c++filt) has been moved to binutils.
 # But make this target work anyway for demangler hacking.

             reply	other threads:[~2015-06-18 20:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-18 20:35 Mike Stump [this message]
2015-06-18 20:55 ` Andreas Schwab
2015-06-18 22:48   ` Mike Stump
2015-11-12 19:25 Mike Stump

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=17242213-EF29-4BDE-929B-AB383C8AA9B2@comcast.net \
    --to=mikestump@comcast.net \
    --cc=gcc-patches@gcc.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).