Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

LilyPond installed by Homebrew fails to produce PDF file #208

Open
thSoft opened this issue Aug 29, 2024 · 1 comment
Open

LilyPond installed by Homebrew fails to produce PDF file #208

thSoft opened this issue Aug 29, 2024 · 1 comment
Assignees
Labels
Milestone

Comments

@thSoft
Copy link
Owner

thSoft commented Aug 29, 2024

Versions:

  • macOS 14.3.1
  • Elysium 0.7.0
  • LilyPond 2.24.4

Steps to reproduce:

  • Install LilyPond via Homebrew with brew install lilypond
  • In the Elysium application, under Preferences > LilyPond > Compiler, set Path to LilyPond executable to /usr/local/bin/lilypond or /usr/local/Cellar/lilypond/2.24.4/bin/lilypond
  • Compile a score

Actual output: No PDF file is created, and the following error appears in the Console:

Converting to `score.pdf'...
warning: g_spawn_sync failed (-1): gs: Failed to execute child process “gs” (No such file or directory)
warning: `(gs -q -dNODISPLAY -dNOSAFER -dNOPAUSE -dBATCH -dAutoRotatePages=/None -dPrinted=false /var/folders/d7/qt541tgd3vzfk32m544ks8mw0000gn/T//lilypond-tmp-788731)' failed (-1)

/usr/local/Cellar/lilypond/2.24.4/share/lilypond/2.24.4/ly/init.ly:65:2: error: Guile signaled an error for the expression beginning here
#
 (let ((book-handler (if (defined? 'default-toplevel-book-handler)
Throw to key `ly-file-failed' with args `()'.
LilyPond terminated in 3,105 seconds.

Expected output: A PDF file is created

Additional info:

@thSoft thSoft self-assigned this Aug 29, 2024
@thSoft thSoft added the bug label Aug 29, 2024
@thSoft thSoft added this to the 0.7.1 milestone Aug 29, 2024
@thSoft
Copy link
Owner Author

thSoft commented Aug 29, 2024

This LilyPond 2.20.0 build works correctly, you can use it as a workaround.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant