-
Notifications
You must be signed in to change notification settings - Fork 3
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
Can't use self-compiled LilyPond #15
Comments
Oops, these error messages are a red herring. LilyPond 2.22 is distributed as a shell script that sets Is there a way to debug what error Frescobaldi gets when trying to execute LilyPond? |
From my understanding, this is expected: The Flatpak application is not supposed to use "host" libraries and cannot see them. The official binaries probably work because they are statically built. |
Ah sorry I forgot to mention: I used Flatseal to grant Frescobaldi access to the whole filesystem. (Permission issues are the topic of #10) |
But still, it will prefer libraries from inside the Flatpak image to those installed in the "host" system |
This doesn't matter. It doesn't do what you think it does. |
OK. Is there a way to do this or should I just give up on it? |
BTW, 2.22 binaries aren't static. I've tried doing what they do (a wrapper shell script setting |
It's still unclear what you are trying to do If your problem is that F37 broke stuff then I'd use |
What I'm trying to do is simple. I have Frescobaldi installed from Flatpak and a LilyPond binary that I compiled from LilyPond master, and I want to use that binary in Flatpak. In parallel, I'm trying to investigate the problem with running Frescobaldi natively, and if that doesn't work, and there is no way to use Flatpak and a self-compiled binary, I will indeed find a way to run Frescobaldi as it was run in Fedora 36. But my problems aren't completely specific to me, so I'm not just interested in my own case (although, I recognize, running self-compiled LilyPond probably isn't very common). |
Unless you compiled it using the same SDK as the flatpak it won't work. (if it does it's a coincidence) I think that was alreay explained in a previous issues. |
I am unable to use self-compiled versions of LilyPond in Frescobaldi from Flatpak. This works fine in "normal" Frescobaldi (well, for me, used to work fine -- the reason I'm switching to Flatpak is that Frescobaldi is broken in Fedora 37 beta due to Python 3.11, so I won't be able to test things with "normal" Frescobaldi). The symptom is that Frescobaldi displays a "stop" symbol when trying to add it.
To understand the failure, I compiled this file in LilyPond 2.22 inside Flatpak Frescobaldi:
It prints this in the log:
If I build with Guile 2 instead of Guile 3, I get
Does Flatpak set environment variables or such related to dynamic loading?
The text was updated successfully, but these errors were encountered: