--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 <[email protected]> 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
