lilypond-user
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: lyluatex failing to start LilyPond


From: Kevin Barry
Subject: Re: lyluatex failing to start LilyPond
Date: Fri, 5 Oct 2018 21:50:49 +0100

Update: after some debugging I was able to verify that this is caused
by a bug in the version of Texlive shipped with Fedora 28 (I was able
to reproduce the issue described here:
https://tex.stackexchange.com/questions/450184/shell-command-error-when-compiling-with-lualatex-shell-escape-in-fedora-28).
It's from a pre-release version of Texlive 2017, which is apparently
what's in Fedora 28. There isn't even an updated version of Texlive in
Fedora's testing repository. I will try installing from TUG directly
and see if the issue goes away.

Kevin
On Thu, 4 Oct 2018 at 18:13, Kevin Barry <address@hidden> wrote:
>
> Hi Urs,
>
> Thank you for taking an interest in this! The output of both commands is 
> below:
>
> address@hidden ~]$ lilypond --version
> GNU LilyPond 2.19.82
>
> Copyright (c) 1996--2015 by
>   Han-Wen Nienhuys <address@hidden>
>   Jan Nieuwenhuizen <address@hidden>
>   and others.
>
> This program is free software.  It is covered by the GNU General Public
> License and you are welcome to change it and/or distribute copies of it
> under certain conditions.  Invoke as `lilypond --warranty' for more
> information.
>
> address@hidden ~]$ /usr/bin/lilypond --version
> GNU LilyPond 2.19.82
>
> Copyright (c) 1996--2015 by
>   Han-Wen Nienhuys <address@hidden>
>   Jan Nieuwenhuizen <address@hidden>
>   and others.
>
> This program is free software.  It is covered by the GNU General Public
> License and you are welcome to change it and/or distribute copies of it
> under certain conditions.  Invoke as `lilypond --warranty' for more
> information.
>
> Kevin
> On Thu, 4 Oct 2018 at 09:00, Urs Liska <address@hidden> wrote:
> >
> >
> >
> > Am 4. Oktober 2018 09:28:27 MESZ schrieb Kevin Barry <address@hidden>:
> > >Hi Samual,
> > >
> > >Thank you for taking the time to respond. I tried running the command
> > >with the --shell-escape option before the file name like so:
> > >  lualatex --shell-escape lyluatest.tex
> > >And I got the same result. I've attached the log to this email in case
> > >anything is different.
> >
> > What happens with
> >   lilypond --version
> > or
> >   /usr/bin/lilypond --version
> >
> > on the command line?
> >
> > Urs
> >
> > >
> > >The error I'm getting is:
> > >usr/share/texlive/texmf-dist/tex/latex/base/ltluatex.lua:
> > >109:
> > >Module lyluatex Error: LilyPond could not be started.
> > >(lyluatex)             Please check that LuaLaTeX is started with the
> > >(lyluatex)             --shell-escape option, and that 'program'
> > >(lyluatex)             points to a valid LilyPond executable.
> > >(lyluatex)             on input line 4
> > >
> > >stack traceback:
> > >[C]: in function 'error'
> > >/usr/share/texlive/texmf-dist/tex/latex/base/ltluatex.lua:109: in
> > >function </u
> > >sr/share/texlive/texmf-dist/tex/latex/base/ltluatex.lua:108>
> > >(...tail calls...)
> > >./lyluatex.lua:898: in function 'lilypond_version'
> > >./lyluatex.lua:1113: in function 'run_lilypond'
> > >./lyluatex.lua:1094: in function 'process'
> > >[\directlua]:1: in main chunk.
> > >address@hidden ...directlua {ly.score:process()}
> > >
> > >l.4 \lilypond{ b }
> > >
> > >Kevin
> > >On Thu, 4 Oct 2018 at 01:29, Br. Samuel Springuel
> > ><address@hidden> wrote:
> > >>
> > >> On 10/3/18 7:09 PM, Kevin Barry wrote:
> > >> > lualatex lyluatest.ly --shell-escape
> > >>
> > >> That's the wrong order.  Options come before the file name.
> > >>
> > >> --
> > >> ✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝
> > >> Br. Samuel, OSB
> > >> (R. Padraic Springuel)
> > >> St. Anselm’s Abbey
> > >> 4501 South Dakota Ave, NE
> > >> Washington, DC, 20017
> > >> 202-269-2300
> > >> (c) 202-853-7036
> > >>
> > >> PAX ☧ ΧΡΙΣΤΟΣ
> > >>
> > >> _______________________________________________
> > >> lilypond-user mailing list
> > >> address@hidden
> > >> https://lists.gnu.org/mailman/listinfo/lilypond-user



reply via email to

[Prev in Thread] Current Thread [Next in Thread]