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.
commit dc3403f07733a847f37e15c856759a94aa7e97d7
Author: Jonathan Wakely <jwak...@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) ;; \
