public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "vapier at gentoo dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/51368] New: libstdc++ python pretty printers should use --with-python-dir just like libjava Date: Wed, 30 Nov 2011 22:02:00 -0000 [thread overview] Message-ID: <bug-51368-4@http.gcc.gnu.org/bugzilla/> (raw) 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
next reply other threads:[~2011-11-30 21:46 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-11-30 22:02 vapier at gentoo dot org [this message] 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
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=bug-51368-4@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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: linkBe 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).