1 |
Yann - |
2 |
|
3 |
I'm not sure about the downgrade from 3.3.6 to 3.3.5, but I had the same |
4 |
problem with libungif. I fixed it by unmerging giflib (emerge --ask |
5 |
--unmerge media-libs/giflib). Then re-running the update, which actually |
6 |
re-installed giflib for me. |
7 |
|
8 |
HTH |
9 |
|
10 |
On 9/14/05, Yann GARNIER <garnier-yann@×××××××.fr> wrote: |
11 |
> |
12 |
> Hi all, |
13 |
> |
14 |
> I did an "emerge -vuD world" last week and, among other thing, it updated |
15 |
> GCC from 3.3.5 to 3.3.6 (which seemed to be a good thing..) |
16 |
> Today after an "emerge --sync" I wanted to re-update my system ... and I'm |
17 |
> wondering why portage 'wants' to downgrade my version of GCC from 3.3.6 |
18 |
> to 3.3.5... but also wondering why it suddenly wants to install giflib |
19 |
> (which is blocked because of libungif...) |
20 |
> The only thing I can do now to update the system is to add "-gif" in my |
21 |
> make.conf file. |
22 |
> |
23 |
> Is there any other way to solve the giflib/libungif conflict ? |
24 |
> |
25 |
> What makes portage want to install giflib ? |
26 |
> |
27 |
> Can someone tell me what I missed ? |
28 |
> |
29 |
> In advance thank you. |
30 |
> |
31 |
> Yann Garnier |
32 |
> |
33 |
> -- |
34 |
> gentoo-user@g.o mailing list |
35 |
> |
36 |
> |