On Monday 15 September 2003 17:16, Lloyd D Budd wrote:
> On Mon, 2003-09-15 at 03:58, Joshua Banks wrote:
> > 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
>
> Possibly remerge this.

I hate to sound rude but... please don't try to give advice unless you have 
advice to give. What does "possibly" mean? Why should he "possible" remerge 
it?

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

Also try to be a bit more clearer... make.defaults is always used. The only 
time it isn't is when you've done like me and have -* at the start of your 
USE in make.conf. Otherwise it serves as the base. Actually, the default 
order can also be changed - look in make.globals to find out how and add the 
change to make.conf if you wish.

> > 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?
>
> Yes

Basically, even a meta-distribution has to have a set of defaults. That's 
where the defaults are kept.

> > 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?
>
> For your modifications to the USE var.

And any other vars...

> > 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"
>
> Better to simply look at the output of 'emerge info'

Again, I think it's better to look at make.defaults. At least then you know 
where the use flags are coming from.


Jason

--
[EMAIL PROTECTED] mailing list

Reply via email to