Wayne Blaszczyk wrote: > On 28/10/11 23:10, Andrew Benton wrote: >>> When I tried to build libxml2, it did not detect Python. >>> libxslt also did not detect Python. >>> I suspect there will be a lot of other packages that will have trouble >>> with Python 3.2.
>> As DJ Lucas said the other day, it's possible to fix some things with >> the 2to3 tool included with python 3. However, there are quite a lot of >> things out there that would need fixing so I personally install both >> Python-2.7.2 and Python-3.2.2 with 2.7.2 as the default >> /usr/bin/python. It's a bit like with gtk+-3, more things are >> starting to use gtk+-3 but I think it'll be a while before I stop >> installing gtk+-2 > Sorry for missing the previous post. > Should we not have both versions in the book then? Are there any naming conflicts between python3 and python2? It looks like I have: /usr/bin: pydoc3 python3 python3.2 python3.2m pydoc3.2 python3-config python3.2-config python3.2m-config /usr/lib: /usr/lib/libpython3.2m.so /usr/lib/libpython3.so /usr/lib/libpython3.2m.so.1.0 /usr/lib/libstdc++.so.6.0.16-gdb.py /usr/lib/python3.2: ... Are there any gotchas in building side-by-side? What build instructions do you use in each case? What packages besides libxml2 and libxslt did not detect python? Personally, I built both before python. I generally don't like python and only build it when I have to (e.g. trac) or for the book. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
