Alpha: glibc - python disaster

HuskyDog · Posted: Thu Oct 09, 2003 10:57 pm Post subject: Alpha: glibc - python disaster

I did an 'emerge -u world' on my Alpha. It downgraded glibc. Now, python complains that the wrong version is installed, thus,

kc8apf · n00b Joined: 10 Oct 2003 Posts: 3

I'm in the same boat. I'm guessing about the only thing we can do is manually build Python using the same method as is used in the ebuild. Hopefully someone else has a better idea.

And 30 lashings with a spaghetti noodle to whoever did the downgrade!

agriffis · Posted: Fri Oct 10, 2003 8:39 pm Post subject: My fault

I confess, I did it. The problem is that glibc 2.3.2 stopped compiling on alpha when gcc 3.3.1 came along. So I marked glibc 2.3.2 ~alpha until we get a version that builds right.

I'll work on that part. Sorry I messed you guys up. :-(

For the moment, I'd suggest using "emerge -U world" instead of -u, but that's a little late for anybody in this forum.

HuskyDog · Posted: Sat Oct 11, 2003 5:19 pm Post subject: Fixed

Well, I have now fixed it.

I untarred the Python source, did a configure --with-fpectl (I got that from the ebuild) and make, make install. That put python into /usr/local (I guess I could have found a configure option to fix that).

Anyway, it turns out that emerge calls /usr/bin/python2.2, so I linked that to my new python. The only other thing I had to do was copy the contents of /usr/lib/python2.2/site-packages into /usr/local/lib/python2.2/site-packages.

emerge then worked, so I quickly emerged python properly.

Since then I have been finding other packages not working properly (libxml2 and vim so far) and rebuilding them.

Phew, that was a close shave!