| 1 |
Thanks a lot Volker. I can emerge nvidia-drivers after resync. |
| 2 |
|
| 3 |
Hung |
| 4 |
|
| 5 |
Volker Armin Hemmann wrote: |
| 6 |
> On Donnerstag 08 Oktober 2009, Hung Dang wrote: |
| 7 |
> |
| 8 |
>> Hi all, |
| 9 |
>> |
| 10 |
>> I updated my system yesterday today and find out that the latest |
| 11 |
>> nvidia-drivers requires old glbc version 2.5. I have goggled for a while |
| 12 |
>> and have not found out the solution. Below is the output of emerge command |
| 13 |
>> |
| 14 |
>> emerge -pv nvidia-drivers |
| 15 |
>> |
| 16 |
>> These are the packages that would be merged, in order: |
| 17 |
>> |
| 18 |
>> Calculating dependencies... done! |
| 19 |
>> [ebuild UD] sys-libs/glibc-2.5-r4 [2.10.1] USE="(multilib) nls |
| 20 |
>> nptl%* nptlonly%* -build% -debug -glibc-compat20% -glibc-omitfp |
| 21 |
>> (-hardened) -profile (-selinux) (-gd%*) (-vanilla%)" 0 kB |
| 22 |
>> [ebuild R ] x11-drivers/nvidia-drivers-185.18.31 USE="acpi gtk |
| 23 |
>> (multilib) -custom-cflags" 0 kB |
| 24 |
>> |
| 25 |
>> Any idea? |
| 26 |
>> |
| 27 |
>> Thanks a lot |
| 28 |
>> Hung Dang |
| 29 |
>> |
| 30 |
>> |
| 31 |
> |
| 32 |
> resync. There is nothing about glibc in the ebuild. |
| 33 |
> |
| 34 |
> see changelog after sync: |
| 35 |
> 06 Oct 2009; Jeroen Roovers <jer@g.o> |
| 36 |
> nvidia-drivers-71.86.09.ebuild, nvidia-drivers-71.86.11.ebuild, |
| 37 |
> nvidia-drivers-96.43.09.ebuild, nvidia-drivers-96.43.11.ebuild, |
| 38 |
> nvidia-drivers-96.43.13.ebuild, nvidia-drivers-173.14.15.ebuild, |
| 39 |
> nvidia-drivers-173.14.18.ebuild, nvidia-drivers-173.14.20.ebuild, |
| 40 |
> nvidia-drivers-180.29.ebuild, nvidia-drivers-180.60.ebuild, |
| 41 |
> nvidia-drivers-185.18.14.ebuild, nvidia-drivers-185.18.29.ebuild, |
| 42 |
> nvidia-drivers-185.18.31.ebuild, nvidia-drivers-190.18.ebuild, |
| 43 |
> nvidia-drivers-190.25.ebuild, nvidia-drivers-190.32.ebuild, |
| 44 |
> nvidia-drivers-190.36.ebuild: |
| 45 |
> Remove elibc_glibc dependency for now as it breaks horribly. |
| 46 |
> |
| 47 |
> |
Archives