1 |
glibc is not backwards compatible... |
2 |
|
3 |
I had a copy of a binary glibc that someone made for me, but I dont' have it |
4 |
anymore :( But that is my suggestion, get someone to make a binary, and |
5 |
have them send it to you... |
6 |
|
7 |
there may be another way, but I don't know... |
8 |
|
9 |
Gene |
10 |
|
11 |
----- Original Message ----- |
12 |
From: <mutex@×××××××.org> |
13 |
To: <gentoo-ppc-dev@g.o> |
14 |
Sent: Thursday, May 15, 2003 1:03 AM |
15 |
Subject: [gentoo-ppc-dev] latest GLIBC borks things beyond belief |
16 |
|
17 |
|
18 |
> so, I have been on irc today complaining about how the latest glibc has |
19 |
> borked my entire system, but I figure maybe people will have more ideas |
20 |
> if I post to the mailing list... |
21 |
> at any rate! |
22 |
> after an emerge sync today, i emerged |
23 |
> binutils-2.13.90.0.16 and unmerged binutils-2.14.90.0.1-r1 |
24 |
> (this must be a portage bug) |
25 |
> and emerged |
26 |
> glibc-2.3.1-r2 and unmerged glibc-2.3.2-r1 |
27 |
> and now my system is totally borked, not a single program seems to be |
28 |
> able to use /lib/libpthread.so.0, and that is the only problem I have |
29 |
> been able to really diagnose, but it looks like execvp is failing. |
30 |
> so.. any ideas would be helpful, am I a freak accident or did I find a |
31 |
> bug in portage ? |
32 |
> Dave |
33 |
|
34 |
|
35 |
-- |
36 |
gentoo-ppc-dev@g.o mailing list |