On Fri Jul 01 23:31:45 2016, noloa...@gmail.com wrote:
> On Wed, Jun 29, 2016 at 5:19 PM, Richard Levitte via RT
> wrote:
> > This has nothing to do with Windows 10 per se, it's the space-in-
> > directory
> > issue that's come back.
> > I'm working on a solution that should avoid that problem mor
On Wed, Jun 29, 2016 at 5:19 PM, Richard Levitte via RT
wrote:
> This has nothing to do with Windows 10 per se, it's the space-in-directory
> issue that's come back.
> I'm working on a solution that should avoid that problem more consistently,
> going forward.
Close it; its good as of fe964f0c88
This has nothing to do with Windows 10 per se, it's the space-in-directory
issue that's come back.
I'm working on a solution that should avoid that problem more consistently,
going forward.
Cheers,
Richard
On Wed Jun 29 09:04:12 2016, noloa...@gmail.com wrote:
> Working on a Windows 10, 32-bit ne
Working on a Windows 10, 32-bit netbook. HEAD,
03cb37acec0c23a01bee4357cd59ec9f97e528ba.
It looks like configure dies if it can't find NASM. Perhpas it would
be better to automatically add no-asm.
Once NASM is added, Configure dies because it tries to write outside
%HOME%. Windows 8 used to toler
