On Thu, May 18, 2017 at 12:31 AM, Marty Plummer <[email protected]> wrote: > On Thu, May 18, 2017 at 07:16:43AM +0300, Alon Bar-Lev wrote: >> On 18 May 2017 at 07:10, Marty Plummer <[email protected]> wrote: >> > On Thu, May 18, 2017 at 06:53:48AM +0300, Alon Bar-Lev wrote: >> >> On 18 May 2017 at 06:54, Marty Plummer <[email protected]> wrote: >> >> > Greetings, >> >> > >> >> > As the subject states, compiling dev-libs/libressl for >> >> > x86_64-w64-mingw32 >> >> > target via crossdev ends up calling wine to run checks, which fails with >> >> > an access violation, and as such emerge cannot finish. >> >> > >> >> > Would it be an acceptable change to disable emake check for mingw-w64 >> >> > crossdev targets? >> >> > >> >> >> >> Why do you enable tests? >> >> >> > I did not, there is no use flag for dev-libs/libressl I can use to >> > disable tests. if there is a global flag I should disable, I'd be >> > greatly appreciative of it. >> > >> >> If you enable tests globally, then you can disable them for a specific >> build using: >> FEATURES="-test" emerge ... >> > it seems that dev-libs/libressl does not respect this action, just tried > again with FEATURES="-test" and had the same result. >
>From your build log, wine is being called during the compile phase, not the test phase, so FEATURES="test" has no effect. In any case, you should file a bug report on bugzilla.
