On Fri, Aug 22, 2014 at 12:41 AM, Ken Moffat <[email protected]> wrote:
> On Thu, Aug 21, 2014 at 09:35:33PM +0530, Hariharan wrote: > > > > My Mesa build on this machine (intel) is slightly different from > > > >the book (I don't have llvm, so I drop the r300 ... radeonsi > > > >drivers) and that file gets created during the build, not by > > > >autogen.sh. > > > > > > > So, I presume you used ./configure > > > > > No, ./autogen.sh, followed by make, like the book says. > > > > > What do you get for > > > >python --version ? You should get Python 2.7.8 > > > > > > > > When i tried building Mesa, it (python) was version 3.4. then i changed > the > > symlink to make it point to python 2.7. > > > > > Setting a Python symlink is a bad mistake - Python-3.4 installs > >Python3 and Python3.4. Some people (gentoo, and I think fedora) > >have tried to only use Python3 - and they have seds, patches, > >breakages to match. For BLFS, we can install both 2 and 3. > > Yeah, learnt a lesson now. > Yeah, Python is unpleasant. > > > >Do you have both > >/usr/lib/python2.7/lib-dynload/pyexpat.so > > and > >/usr/lib/python2.7/xml/parsers/expat.py ? > Problem solved, I didn't have pyexpat.so , so i rebuilt python 2.7 . Worked like a charm. Now I understand what went wrong.. I hadn't installed expat when I installed python as it was only recommended and not required. Then, when the MesaLib build failed I tried installing expat, but that didn't solve the problem. So after Christopher suggested re-installing python, which I did. So expat -> python2.7 -> MesaLib = success. Thanks a lot Ken and Christopher. BTW, Armin, the --with-system-expat switch wasn't required as python already had the expat module. > -- *Hari*
-- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
