| 1 |
Kyung-hwan Kim wrote: |
| 2 |
> |
| 3 |
> > Hmm seems like the uploaded package was build with binutils-2.1.10. |
| 4 |
> > I made a new package for binutils-2.1.10.91.0.2 that fixes some ld |
| 5 |
> > segfaults. |
| 6 |
> > With that binutils version I build a new glibc-2.2.2 package (r1). |
| 7 |
> > This should not give you segfaults. It works here for me. But many packages |
| 8 |
> > do not compile |
| 9 |
> > with glibc-2.2.2 because the headers have changed. |
| 10 |
> |
| 11 |
> After merging binutils-2.10.1.0.7 and everything gose beautifully. |
| 12 |
> But merging glibc-2.2.2, nothing would go its way. |
| 13 |
> |
| 14 |
> Do you mean that packages must be recompiled under glibc-2.2.2 and |
| 15 |
> updated binutils environment? |
| 16 |
No normaly that should not be neccesary. |
| 17 |
|
| 18 |
It seems that the problem is arch dependend. |
| 19 |
|
| 20 |
I use i686-pc-linux-gnu here. The rc4_pre2 packages use |
| 21 |
i486-pc-linux-gnu |
| 22 |
as default. |
| 23 |
|
| 24 |
I currently building glibc-2.2.2-r1 with binutils-2.10.92.0.2 on a pure |
| 25 |
rc4_pre2 machine. I hope that works. |
| 26 |
|
| 27 |
Did the glibc test's fail on your machine when using binutils 2.10.1? |
| 28 |
|
| 29 |
On a i686 target they do. |
| 30 |
|
| 31 |
achim~ |
| 32 |
> If so, no non-developer gentoo user can succeed in upgrading glibc. |
| 33 |
> |
| 34 |
> Kyunghwan |
| 35 |
> |
| 36 |
> _______________________________________________ |
| 37 |
> gentoo-dev mailing list |
| 38 |
> gentoo-dev@g.o |
| 39 |
> http://www.gentoo.org/mailman/listinfo/gentoo-dev |
Archives