public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
* [gentoo-user] emerge --update --newuse too eager?
@ 2009-07-13  7:11 Helmut Jarausch
  2009-07-13  7:24 ` Alan McKinnon
  2009-07-13  8:30 ` Eray Aslan
  0 siblings, 2 replies; 4+ messages in thread
From: Helmut Jarausch @ 2009-07-13  7:11 UTC (permalink / raw
  To: gentoo-user

Hi,

would anybody please be so kind to explain to me how
emerge --update --newuse --deep @system @world
works.

E.g. it wants to  re-emerge sys-devel/gcc because of the
"new use flag nptl"  according to

[ebuild   R   ] sys-devel/gcc-4.4.0  USE="nptl%*" 
[ebuild   R   ] sys-devel/gcc-4.3.3-r2  USE="nptl%*" 

But, looking at the corresponding ebuild files they don't
use (IUSE or other) such a use flag.
But why then does emerge want to rebuild those packages.?

(I'm using portage 2.2_rc33)

Many thanks for an explanation,
Helmut.

-- 
Helmut Jarausch

Lehrstuhl fuer Numerische Mathematik
RWTH - Aachen University
D 52056 Aachen, Germany



^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [gentoo-user] emerge --update --newuse too eager?
  2009-07-13  7:11 [gentoo-user] emerge --update --newuse too eager? Helmut Jarausch
@ 2009-07-13  7:24 ` Alan McKinnon
  2009-07-13  8:30 ` Eray Aslan
  1 sibling, 0 replies; 4+ messages in thread
From: Alan McKinnon @ 2009-07-13  7:24 UTC (permalink / raw
  To: gentoo-user

On Monday 13 July 2009 09:11:04 Helmut Jarausch wrote:
> Hi,
>
> would anybody please be so kind to explain to me how
> emerge --update --newuse --deep @system @world
> works.
>
> E.g. it wants to  re-emerge sys-devel/gcc because of the
> "new use flag nptl"  according to
>
> [ebuild   R   ] sys-devel/gcc-4.4.0  USE="nptl%*"
> [ebuild   R   ] sys-devel/gcc-4.3.3-r2  USE="nptl%*"
>
> But, looking at the corresponding ebuild files they don't
> use (IUSE or other) such a use flag.
> But why then does emerge want to rebuild those packages.?
>
> (I'm using portage 2.2_rc33)
>
> Many thanks for an explanation,
> Helmut.

It's from an inherited eclass:

# grep inherit *
gcc-4.3.3-r2.ebuild:inherit toolchain
gcc-4.4.0.ebuild:inherit toolchain
nazgul gcc # grep nptl /var/portage/eclass/toolchain.eclass
        IUSE="multislot nptl test"
                confgcc="${confgcc} --disable-__cxa_atexit --enable-target-
optspace $(use_enable nptl tls)"

-- 
alan dot mckinnon at gmail dot com



^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [gentoo-user] emerge --update --newuse too eager?
  2009-07-13  7:11 [gentoo-user] emerge --update --newuse too eager? Helmut Jarausch
  2009-07-13  7:24 ` Alan McKinnon
@ 2009-07-13  8:30 ` Eray Aslan
  2009-07-13  8:32   ` Hazen Valliant-Saunders
  1 sibling, 1 reply; 4+ messages in thread
From: Eray Aslan @ 2009-07-13  8:30 UTC (permalink / raw
  To: gentoo-user

On 13.07.2009 10:11, Helmut Jarausch wrote:
> would anybody please be so kind to explain to me how
> emerge --update --newuse --deep @system @world
> works.
> 
> E.g. it wants to  re-emerge sys-devel/gcc because of the
> "new use flag nptl"  according to
> 
> [ebuild   R   ] sys-devel/gcc-4.4.0  USE="nptl%*" 
> [ebuild   R   ] sys-devel/gcc-4.3.3-r2  USE="nptl%*" 
> 
> But, looking at the corresponding ebuild files they don't
> use (IUSE or other) such a use flag.
> But why then does emerge want to rebuild those packages.?

nptl USE flag comes from toolchain.eclass.  Almost all the work for the
ebuild is done in the toolchain.eclass for gcc.

nptl flag was recently added to enable thred local storage for
nptl/uclibc users:
http://sources.gentoo.org/viewcvs.py/gentoo-x86/eclass/toolchain.eclass?r1=1.400&r2=1.401

-- 
Eray



^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [gentoo-user] emerge --update --newuse too eager?
  2009-07-13  8:30 ` Eray Aslan
@ 2009-07-13  8:32   ` Hazen Valliant-Saunders
  0 siblings, 0 replies; 4+ messages in thread
From: Hazen Valliant-Saunders @ 2009-07-13  8:32 UTC (permalink / raw
  To: gentoo-user

[-- Attachment #1: Type: text/plain, Size: 1113 bytes --]

--deep (rebuilds the compiler)  and it looks like you've built two versions
of GCC in the past.

On Mon, Jul 13, 2009 at 4:30 AM, Eray Aslan <eray.aslan@caf.com.tr> wrote:

> On 13.07.2009 10:11, Helmut Jarausch wrote:
> > would anybody please be so kind to explain to me how
> > emerge --update --newuse --deep @system @world
> > works.
> >
> > E.g. it wants to  re-emerge sys-devel/gcc because of the
> > "new use flag nptl"  according to
> >
> > [ebuild   R   ] sys-devel/gcc-4.4.0  USE="nptl%*"
> > [ebuild   R   ] sys-devel/gcc-4.3.3-r2  USE="nptl%*"
> >
> > But, looking at the corresponding ebuild files they don't
> > use (IUSE or other) such a use flag.
> > But why then does emerge want to rebuild those packages.?
>
> nptl USE flag comes from toolchain.eclass.  Almost all the work for the
> ebuild is done in the toolchain.eclass for gcc.
>
> nptl flag was recently added to enable thred local storage for
> nptl/uclibc users:
>
> http://sources.gentoo.org/viewcvs.py/gentoo-x86/eclass/toolchain.eclass?r1=1.400&r2=1.401
>
> --
> Eray
>
>


-- 
Hazen Valliant-Saunders
IT/IS Consultant
(613) 355-5977

[-- Attachment #2: Type: text/html, Size: 1716 bytes --]

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2009-07-13  8:32 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-07-13  7:11 [gentoo-user] emerge --update --newuse too eager? Helmut Jarausch
2009-07-13  7:24 ` Alan McKinnon
2009-07-13  8:30 ` Eray Aslan
2009-07-13  8:32   ` Hazen Valliant-Saunders

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox