luxInteg wrote: > I compiled and installed Python-2.7.1 without valgrind support > (which would not compile on linux-3.x. I then got got valgrind to > compile. So I have this question:- > > I know Python can be finnicky so is it necessary to yank out the > installed copy of Python-2.7.1 before installing that which was > built with valgrind or is installing over sufficient?
Just to be clear, do you mean that you have rebuilt Python with valgrind support, you want to install your new Python, and you are wondering if the presence of the old Python means that you have to do more than just install the new Python? I am 99.9% sure the answer is "No". Just re-installing will be fine. I have not tested this but I have searched the Python source and the only effect of enabling valgrind support is to change the way Python allocates memory for objects when it is running under valgrind. So installing your new Python will just replace your old Python executable with a new one that behaves in exactly the same way except when it is running under valgrind. By the way, no matter what the consequences of enabling valgrind support I would call it a severe bug in the build system if the standard install procedure broke just because there was already an older or differently configured version of the software installed on the system. In other words, "install" should do what it says on the tin. Regards, Jeremy Henty -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
