> > I resorted to using WSL out of desperation on a system where I can't
> > get the wifi to work on Linux. I was able to develop on LilyPond more
> > or less unhindered (until I checked again recently). If you have a
> > Linux system there's no reason to use WSL (IMO).
>
> Quite.
The final irony
Hello,
On 17/06/2021 11:44, Kevin Barry wrote:
Hi James,
I cannot even get autogen.sh to run!
-bash: ./autogen.sh: /bin/sh^M: bad interpreter: No such file or directory
This appears to be caused by a line ending difference betwen *nix and
Windows.
That's odd; did you clone the repo from w
Hi James,
> I cannot even get autogen.sh to run!
>
>
> -bash: ./autogen.sh: /bin/sh^M: bad interpreter: No such file or directory
>
> This appears to be caused by a line ending difference betwen *nix and
> Windows.
That's odd; did you clone the repo from within WSL or from Windows?
>
> Ugh. So m
Le 17/06/2021 à 10:45, James a écrit :
Hello,
On 12/06/2021 11:01, James wrote:
Kevin,
On 12/06/2021 10:02, Kevin Barry wrote:
OK well something must have changed since I last did a build on WSL
because I couldn't even get `make all' on a freshly checked out master
to work. And that was *d
Hello,
On 12/06/2021 11:01, James wrote:
Kevin,
On 12/06/2021 10:02, Kevin Barry wrote:
OK well something must have changed since I last did a build on WSL
because I couldn't even get `make all' on a freshly checked out master
to work. And that was *definitely* working before.
It fails now wi
Kevin,
On 12/06/2021 10:02, Kevin Barry wrote:
OK well something must have changed since I last did a build on WSL
because I couldn't even get `make all' on a freshly checked out master
to work. And that was *definitely* working before.
It fails now with this error:
Making Documentation/out/en/
OK well something must have changed since I last did a build on WSL
because I couldn't even get `make all' on a freshly checked out master
to work. And that was *definitely* working before.
It fails now with this error:
Making Documentation/out/en/changes.texi < tely
lilypond-book.py: error: file
Hi James,
I'm pretty sure that I managed this, but I may not have gone as far as
a full doc build, but I think I managed install-info. I will try to
make time to verify and get back to you.
Kevin
On Wed, 9 Jun 2021 at 07:37, James wrote:
>
> Hello,
>
> Has anyone on this list recently (within t
