This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: gdb pretty-printers for libstdc++
- From: Gerald Pfeifer <gerald at pfeifer dot com>
- To: gcc-patches at gcc dot gnu dot org, libstdc++ at gcc dot gnu dot org, Tom Tromey <tromey at redhat dot com>, Phil Muldoon <pmuldoon at redhat dot com>, Jonathan Wakely <jwakely dot gcc at gmail dot com>
- Date: Fri, 29 May 2009 13:31:44 +0200 (CEST)
- Subject: Re: gdb pretty-printers for libstdc++
After this patch
2009-05-28 Tom Tromey <tromey@redhat.com>
Phil Muldoon <pmuldoon@redhat.com>
Jonathan Wakely <jwakely.gcc@gmail.com>
* python/Makefile.in, , python/libstdcxx/__init__.py,
python/libstdcxx/v6/__init__.py, python/libstdcxx/v6/printers.py,
python/hook.in, python/Makefile.am: New files.
* configure, Makefile.in: Rebuild.
* acinclude.m4 (glibcxx_SUBDIRS): Add python.
* Makefile.am (SUBDIRS): Add python.
we have
share/libstdc++/python/libstdcxx/__init__.py
share/libstdc++/python/libstdcxx/v6/__init__.py
share/libstdc++/python/libstdcxx/v6/printers.py
under $PREFIX which will create conflicts when installing several
versions of GCC under the same $PREFIX.
This is common practice under FreeBSD, for example, where the ports
have been using --program-suffix, --libdir, --libexecdir just fine for
many years.
I filed PR #40289 to track this.
Gerald
PS: I didn't see this on gcc-patches, or I would have reported this
earlier. This was caught by my weekly packaging testing now.