1 |
On Thu, May 18, 2017 at 12:31 AM, Marty Plummer <netz.kernel@×××××.com> wrote: |
2 |
> On Thu, May 18, 2017 at 07:16:43AM +0300, Alon Bar-Lev wrote: |
3 |
>> On 18 May 2017 at 07:10, Marty Plummer <netz.kernel@×××××.com> wrote: |
4 |
>> > On Thu, May 18, 2017 at 06:53:48AM +0300, Alon Bar-Lev wrote: |
5 |
>> >> On 18 May 2017 at 06:54, Marty Plummer <netz.kernel@×××××.com> wrote: |
6 |
>> >> > Greetings, |
7 |
>> >> > |
8 |
>> >> > As the subject states, compiling dev-libs/libressl for x86_64-w64-mingw32 |
9 |
>> >> > target via crossdev ends up calling wine to run checks, which fails with |
10 |
>> >> > an access violation, and as such emerge cannot finish. |
11 |
>> >> > |
12 |
>> >> > Would it be an acceptable change to disable emake check for mingw-w64 |
13 |
>> >> > crossdev targets? |
14 |
>> >> > |
15 |
>> >> |
16 |
>> >> Why do you enable tests? |
17 |
>> >> |
18 |
>> > I did not, there is no use flag for dev-libs/libressl I can use to |
19 |
>> > disable tests. if there is a global flag I should disable, I'd be |
20 |
>> > greatly appreciative of it. |
21 |
>> > |
22 |
>> |
23 |
>> If you enable tests globally, then you can disable them for a specific |
24 |
>> build using: |
25 |
>> FEATURES="-test" emerge ... |
26 |
>> |
27 |
> it seems that dev-libs/libressl does not respect this action, just tried |
28 |
> again with FEATURES="-test" and had the same result. |
29 |
> |
30 |
|
31 |
From your build log, wine is being called during the compile phase, |
32 |
not the test phase, so FEATURES="test" has no effect. |
33 |
|
34 |
In any case, you should file a bug report on bugzilla. |