New submission from Matthias Klose <d...@debian.org>: currently, much of the configuration information is fetched by opening the config.h and the Makefile for the build. The locations of these files are derived from the prefix given at configure time.
If you want to have two distinct builds with the same prefix, but with different configuration options, this kind of configuration information is unsufficient. The current use case is a normal build and a debug build, as used for the Fedora and Debian/Ubuntu python packages. Fedora and Debian/Ubuntu carry a patch, adding a sys.pydebug attribute and patching "some" things to get the correct information for these builds using the same prefix. This kind of information should not be derived by following some paths names, but be contained in the python binary itself, without needing to read the Makefile and the config.h files. Attached is a patch currently applied in Debian/Ubuntu (and some variant for Fedora) which introduces a sys.pydebug attribute and derives the correct locations for the config.h and Makefile files. It's not meant as a patch ready to apply, but to get an idea what is needed to have two different python installations with the same prefix. ---------- components: Build files: debug-build.diff keywords: patch messages: 115923 nosy: barry, doko priority: normal severity: normal stage: needs patch status: open title: deriving configuration information for different builds with the same prefix type: behavior versions: Python 3.2 Added file: http://bugs.python.org/file18807/debug-build.diff _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue9807> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
