1 |
Thank you all for the help. |
2 |
|
3 |
I saw a "bindist" in my global USE flag ! |
4 |
|
5 |
I really don't remember when I had that. May be when I saw it for the |
6 |
first time, I said to me "Hey a weak protocol (EC)? disable it !" … |
7 |
|
8 |
For the moment, no more problem ! |
9 |
|
10 |
|
11 |
Thank you !!!! |
12 |
|
13 |
|
14 |
On 02/06/2017 11:34, Kent Fredric wrote: |
15 |
> On Fri, 2 Jun 2017 10:55:51 +0200 |
16 |
> Hogren <hogren@×××××.com> wrote: |
17 |
> |
18 |
>> dev-libs/openssl:0 |
19 |
>> |
20 |
>> (dev-libs/openssl-1.0.2k:0/0::gentoo, ebuild scheduled for merge) |
21 |
>> pulled in by |
22 |
>> dev-libs/openssl:0[bindist=] required by |
23 |
>> (dev-qt/qtnetwork-5.6.2:5/5.6::gentoo, ebuild scheduled for merge) |
24 |
>> |
25 |
>> ^^^^^^^^ |
26 |
>> |
27 |
>> |
28 |
>> (dev-libs/openssl-1.0.2k:0/0::gentoo, installed) pulled in by |
29 |
>> >=dev-libs/openssl-0.9.8f:0[bindist=] required by |
30 |
>> (net-misc/openssh-7.3_p1-r7:0/0::gentoo, installed) |
31 |
>> |
32 |
> The important thing here is not the version, but the use requirement in |
33 |
> the [ ] |
34 |
> |
35 |
> Consulting `man 5 ebuild` , |
36 |
> |
37 |
>> foo[bar=] bar? ( foo[bar] ) !bar? ( foo[-bar] ) |
38 |
> So, this means that: |
39 |
> |
40 |
> dev-libs/openssl:0[bindist=] required by net-misc/openssh-7.3_p1-r7:0/0::gentoo |
41 |
> |
42 |
> Interprets as: |
43 |
> |
44 |
> is net-misc/openssh built with USE=bindist? |
45 |
> yes -> |
46 |
> require dev-libs/openssl be built with USE=bindist |
47 |
> no -> |
48 |
> require dev-libs/openssl be built WITHOUT USE=bindist |
49 |
> |
50 |
> In short, the USE setting for openssl and openssh must have the same |
51 |
> value for USE=bindist |
52 |
> |
53 |
> And also, dev-qt/qtnetwork also has the same constraint. |
54 |
> |
55 |
> Thus, you need to configure the USE=bindist flag for all of: |
56 |
> |
57 |
> dev-libs/openssl |
58 |
> dev-qt/qtnetwork |
59 |
> net-misc/openssh |
60 |
> |
61 |
> Either be all USE=bindist or USE=-bindist |
62 |
> |
63 |
> *hopefully* that's enough information for you to solve your issue, |
64 |
> but if not, I can expand upon request, if you state what parts you |
65 |
> don't understand |
66 |
> :) |
67 |
> |