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
Yes, it would be sensible to make the same option work for both. Tom, Benjamin, any objections to this? I can try to look into it, but it probably won't be soon.
Author: bkoz Date: Wed Feb 15 19:56:07 2012 New Revision: 184282 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=184282 Log: 2012-02-15 Benjamin Kosnik <bkoz@redhat.com> PR libstdc++/51368 * acinclude.m4 (GLIBCXX_ENABLE_PYTHON): New. * configure.ac: Use it. * python/Makefile.am: Same. * configure: Regenerate. * python/Makefile.in: Regenerate. * Makefile.in: Same. * doc/Makefile.in: Same. * include/Makefile.in: Same. * po/Makefile.in: Same. * src/Makefile.in: Same. * src/c++11/Makefile.in: Same. * src/c++98/Makefile.in: Same. * testsuite/Makefile.in: Same. Modified: trunk/libstdc++-v3/ChangeLog trunk/libstdc++-v3/Makefile.in trunk/libstdc++-v3/acinclude.m4 trunk/libstdc++-v3/configure trunk/libstdc++-v3/configure.ac trunk/libstdc++-v3/doc/Makefile.in trunk/libstdc++-v3/include/Makefile.in trunk/libstdc++-v3/libsupc++/Makefile.in trunk/libstdc++-v3/po/Makefile.in trunk/libstdc++-v3/python/Makefile.am trunk/libstdc++-v3/python/Makefile.in trunk/libstdc++-v3/src/Makefile.in trunk/libstdc++-v3/src/c++11/Makefile.in trunk/libstdc++-v3/src/c++98/Makefile.in trunk/libstdc++-v3/testsuite/Makefile.in
Mine.
This probably needs changing http://gcc.gnu.org/install/configure.html
all but doc
fixed