public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jonathan Wakely <jwakely@redhat.com>
To: libstdc++@gcc.gnu.org, gcc-patches@gcc.gnu.org
Cc: Matthias Klose <doko@ubuntu.com>
Subject: [patch] Restore installation of libstdc++.so.6.0.??-gdb.py
Date: Thu, 20 Aug 2015 10:52:00 -0000	[thread overview]
Message-ID: <20150820105010.GO27791@redhat.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 360 bytes --]

Matthias noticed that my backport of the Filesystem library removed
the libstdc++.so.6.0.21-gdb.py file, which was now getting installed
as libstdc++fs.a-gdb.py instead.

Fixed by changing the glob we use to find the candidate library files
that we use for the name of the installed gdb.py file.

Tested powerpc64le-linux, committed to trunk and gcc-5-branch.

[-- Attachment #2: patch.txt --]
[-- Type: text/x-patch, Size: 784 bytes --]

commit dc3403f07733a847f37e15c856759a94aa7e97d7
Author: Jonathan Wakely <jwakely@redhat.com>
Date:   Thu Aug 20 11:11:51 2015 +0100

    	* python/Makefile.am: Ensure gdb.py is installed for libstdc++ not
    	libstdc++fs.
    	* python/Makefile.in: Regenerate.

diff --git a/libstdc++-v3/python/Makefile.am b/libstdc++-v3/python/Makefile.am
index 5d78224..ccb9427 100644
--- a/libstdc++-v3/python/Makefile.am
+++ b/libstdc++-v3/python/Makefile.am
@@ -49,7 +49,7 @@ install-data-local: gdb.py
 ## fragile, but there does not seem to be a better option, because
 ## libtool hides the real names from us.
 	@here=`pwd`; cd $(DESTDIR)$(toolexeclibdir); \
-	  for file in libstdc++*; do \
+	  for file in libstdc++.*; do \
 	    case $$file in \
 	      *-gdb.py) ;; \
 	      *.la) ;; \

                 reply	other threads:[~2015-08-20 10:50 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=20150820105010.GO27791@redhat.com \
    --to=jwakely@redhat.com \
    --cc=doko@ubuntu.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=libstdc++@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).