On Thu, May 18, 2017 at 12:31 AM, Marty Plummer wrote:
> On Thu, May 18, 2017 at 07:16:43AM +0300, Alon Bar-Lev wrote:
>> On 18 May 2017 at 07:10, Marty Plummer wrote:
>> > On Thu, May 18, 2017 at 06:53:48AM +0300, Alon Bar-Lev wrote:
>> >> On 18 May 2017 at 06:54, Marty Plummer wrote:
>> >> > G
On Thu, May 18, 2017 at 07:16:43AM +0300, Alon Bar-Lev wrote:
> On 18 May 2017 at 07:10, Marty Plummer wrote:
> > On Thu, May 18, 2017 at 06:53:48AM +0300, Alon Bar-Lev wrote:
> >> On 18 May 2017 at 06:54, Marty Plummer wrote:
> >> > Greetings,
> >> >
> >> > As the subject states, compiling dev-l
On 18 May 2017 at 07:10, Marty Plummer wrote:
> On Thu, May 18, 2017 at 06:53:48AM +0300, Alon Bar-Lev wrote:
>> On 18 May 2017 at 06:54, Marty Plummer wrote:
>> > Greetings,
>> >
>> > As the subject states, compiling dev-libs/libressl for x86_64-w64-mingw32
>> > target via crossdev ends up calli
On Thu, May 18, 2017 at 06:53:48AM +0300, Alon Bar-Lev wrote:
> On 18 May 2017 at 06:54, Marty Plummer 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
On 18 May 2017 at 06:54, Marty Plummer 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
