public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug libstdc++/51368] New: libstdc++ python pretty printers should use --with-python-dir just like libjava
@ 2011-11-30 22:02 vapier at gentoo dot org
  2011-12-03  0:50 ` [Bug libstdc++/51368] " redi at gcc dot gnu.org
                   ` (5 more replies)
  0 siblings, 6 replies; 7+ messages in thread
From: vapier at gentoo dot org @ 2011-11-30 22:02 UTC (permalink / raw)
  To: gcc-bugs

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51368

             Bug #: 51368
           Summary: libstdc++ python pretty printers should use
                    --with-python-dir just like libjava
    Classification: Unclassified
           Product: gcc
           Version: unknown
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: libstdc++
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: vapier@gentoo.org


the libjava code already has a useful configure flag for controlling where its
python code is installed (--with-python-dir).  the libstdc++-v3 should use this
same flag so package maintainers need not set the same path in multiple places.

libjava/configure.ac:
default_python_dir="/share/gcc-`cat ${srcdir}/../gcc/BASE-VER`/python/libjava"

libstdc++-v3/python/Makefile.am:
pythondir = $(datadir)/gcc-$(gcc_version)/python


^ permalink raw reply	[flat|nested] 7+ messages in thread

end of thread, other threads:[~2012-02-21  0:23 UTC | newest]

Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2011-11-30 22:02 [Bug libstdc++/51368] New: libstdc++ python pretty printers should use --with-python-dir just like libjava vapier at gentoo dot org
2011-12-03  0:50 ` [Bug libstdc++/51368] " redi at gcc dot gnu.org
2012-02-15 20:13 ` bkoz at gcc dot gnu.org
2012-02-15 20:20 ` bkoz at gcc dot gnu.org
2012-02-15 20:33 ` bkoz at gcc dot gnu.org
2012-02-16 20:45 ` bkoz at gcc dot gnu.org
2012-02-21  0:57 ` bkoz at gcc dot gnu.org

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).