1 |
Hello, |
2 |
|
3 |
I have nptl and nptlonly set in my make.conf file. |
4 |
I thought that was the best setting for threading. |
5 |
|
6 |
|
7 |
Now, I want to install the Chromium web browser. |
8 |
It is asking me to the set the +threads flag for ffmpeg, |
9 |
before www-client/chromium can be installed. OK |
10 |
no problem on a per package basis. |
11 |
|
12 |
But, this has made me think. Is setting nptl and |
13 |
nptl globally (in make.conf) the best idea? |
14 |
|
15 |
Should the threads flag also be set globally, or just |
16 |
on a per package basis? Maybe nptl and threads |
17 |
and not set nptlonly? |
18 |
|
19 |
I thought nptl and nptl was the end of the |
20 |
requirements, but running this command: |
21 |
|
22 |
euse -i threads |
23 |
Here is a curious response; ffmpeg does not get |
24 |
listed (as it is not built with the threads flag)? |
25 |
|
26 |
euse -I threads |
27 |
|
28 |
I see lots of packages where the flag "threads" |
29 |
is being used including ffmpeg. |
30 |
|
31 |
|
32 |
Some discussion and guidance as to how best |
33 |
to set the flags [nptl, nptlonly and threads] |
34 |
(any others related to threading) would be |
35 |
appreciated. |
36 |
|
37 |
|
38 |
James |