Hi all,

Quick question about a little hiccup in a Python installation:

If you use some sort of package manager and remove an existing Python
installation (but preserved all the add-on modules you've installed
since the initial Python installation), you'll have an existing
/usr/lib/python2.5 directory.

Now, if one of the add-on modules you've installed happens to be the
PyXML module, then the test suite for Python will fail with a segfault
while testing the test_pyexpat.py test.

Even though /usr/lib/python2.5 is not in the PYTHONPATH (in fact
that envar was unset before I started the Python installation), you'll
see this failure.

The only way I was able to fix it is to rename the /usr/lib/python2.5
directory before building the package and running 'make test', then
renaming it back to /usr/lib/python2.5 before 'make install'.

Does anyone know a cleaner way to make Python build/run tests without
having to rename the /usr/lib/python2.5 directory?

TIA for any information you may have.

-- 
Randy

rmlscsi: [bogomips 1003.22] [GNU ld version 2.16.1] [gcc (GCC) 4.0.3]
[GNU C Library stable release version 2.3.6] [Linux 2.6.14.3 i686]
08:14:00 up 28 days, 23:02, 1 user, load average: 0.01, 0.03, 0.03
-- 
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to