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