| 1 |
Graham Murray wrote: |
| 2 |
> Zac Medico <zmedico@×××××.com> writes: |
| 3 |
> |
| 4 |
> |
| 5 |
>>Note that it is not necessary to remerge anything other than glibc |
| 6 |
>>when the nptlonly flag is flipped because the nptl threading library |
| 7 |
>>is supposed to be compatible with linuxthreads. |
| 8 |
> |
| 9 |
> |
| 10 |
> While in the main that is true, nptl is not completely compatible (eg |
| 11 |
> signal handling) with the old Linuxthreads. glibc is not the only |
| 12 |
> ebuild to USE the nptl flag, so maybe these ebuilds might need to be |
| 13 |
> re-emerged as well. |
| 14 |
|
| 15 |
Actually, I meant to say "when nptlonly and nptl flags are flipped together". When they are flipped simultaneously, there is only one threading implementation installed (nptl is installed directly in /lib rather than /lib/tls). |
| 16 |
|
| 17 |
As long as the packages that support the nptl USE flag were built with nptlonly and nptl both enabled or both disabled (together, simultaneously), they should not need to be rebuilt because both threading implementations should be binary compatible (though they behave differently). |
| 18 |
|
| 19 |
Zac |
| 20 |
-- |
| 21 |
gentoo-user@g.o mailing list |
Archives