| 1 |
On Saturday 29 October 2005 17:20, Uwe Thiem wrote: |
| 2 |
> On 29 October 2005 17:53, Peter Ruskin wrote: |
| 3 |
> > Well, this is what I did: |
| 4 |
> > |
| 5 |
> > While I still had libubgif, I copied these files to a safe |
| 6 |
> > place: libungif.a libungif.la libungif.so libungif.so.4 |
| 7 |
> > libungif.so.4.1.3 ungif.README |
| 8 |
> > |
| 9 |
> > ...then I humoured portage by unmerging libubgif and emerging |
| 10 |
> > giflib. |
| 11 |
> > |
| 12 |
> > After that I copied the saved libungif files to /usr/lib/ and |
| 13 |
> > now kuickshow works again. So far nothing broke. |
| 14 |
> |
| 15 |
> Well, that's a quick and dirty hack. Alright, this is what really |
| 16 |
> solved it: |
| 17 |
> |
| 18 |
> emerge --unmerge libungif |
| 19 |
> emerge giflib |
| 20 |
> emerge imlib <- that's the important part |
| 21 |
> emerge --update world |
| 22 |
> |
| 23 |
> ... and all are happy. |
| 24 |
> |
| 25 |
Correct, it was dirty. I've since found out that libungif can |
| 26 |
coexist with giflib if you have "-gif" in your USE flags. I |
| 27 |
finally settled with "gif" USE flag and: |
| 28 |
|
| 29 |
# emerge -C libungif |
| 30 |
# emerge -v giflib imlib kuickshow |
| 31 |
|
| 32 |
-- |
| 33 |
Peter |
| 34 |
======================================================================== |
| 35 |
Gentoo Linux: Portage 2.0.51.22-r3. kernel-2.6.13-gentoo-r4. |
| 36 |
i686 AMD Athlon(tm) XP 3200+. gcc(GCC): 3.3.5-20050130. |
| 37 |
KDE: 3.4.3. Qt: 3.3.4. |
| 38 |
======================================================================== |
| 39 |
-- |
| 40 |
gentoo-user@g.o mailing list |
Archives