When I,
bash-2.05b# emerge  libungif
Calculating dependencies ...done!
>>> emerge (1 of 1) media-libs/libungif-4.1.0.1b to /

It unpacks source and does its thing and then says this at the end....


* You had the gif USE flag set, so it is assumed that you want
 * the binary from giflib instead.  Please make sure you have
 * giflib emerged.  Otherwise, unset the gif flag and remerge this
>>> Regenerating /etc/ld.so.cache...
>>> media-libs/libungif-4.1.0.1b merged.
>>> Recording media-libs/libungif in "world" favorites file...
>>> clean: No packages selected for removal.

>>> Regenerating /etc/ld.so.cache...
>>> Auto-cleaning packages ...

>>> No outdated packages were found on your system.


 * GNU info directory index is up-to-date.

I already have media-libs/giflib emerged:
Latest version available: 4.1.0-r3
      Latest version installed: 4.1.0-r3
      Size of downloaded files: 294 kB

So now I'm assuming that since make.conf USE section is commented with # then its using
make.profile and sourcing make.defaults? NO? 

Alittle confused now as to why it's looking here when I don't remember making this 
file or making
a symlink to this file..Is your system setup like this?

lrwxrwxrwx    1 root     root           39 Sep 11 17:42 make.profile ->
../usr/portage/profiles/default-x86-1.4

So if its using this file below then whats the use of make.conf? 


bash-2.05b#less make.defaults

USE="x86 oss apm arts avi berkdb crypt cups encode foomaticdb gdbm gif gpm gtk imlib
java jpeg kde gnome libg++ libwww mad mikmod mmx motif mpeg ncurses nls oggvorbis
opengl pam pdflib png python qt quicktime readline sdl slang spell ssl
svga tcpd truetype X xml2 xmms xv zlib"

ARCH="x86"
COMPILER="gcc3"
ACCEPT_KEYWORDS="x86"


Do I just leave everthing alone and try and emerge KDEgraphics again or should I go 
into the file
above and UNSET "gif"?


JBanks



__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com

--
[EMAIL PROTECTED] mailing list

Reply via email to