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