-
Notifications
You must be signed in to change notification settings - Fork 236
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
Compilation error on Flathub #3620
Comments
All dependencies are listed in the wiki. You can also check the brew formula as an example. I'm not sure about the failure on arm, but on x86 it looks like lapack wasn't found. |
Yes, it mentions that it is not found even though it is in the PATH and the error does not occur in arm. |
Can you access the build artifacts? In particular Alternatively, how do you attempt to build a Flatpak app locally? Also, I'm very confused: what do LyX and its SweaveKnitr plugin have to do with Macaulay2? |
The files in question cannot be accessed from flatpak services. On my PC, the compilation takes a long time and fails due to lack of ram, and it doesn't even reach macaulay2. I'll add an extra module. I use lyx because it's the closest to the texmacs environment. I want to add some extra programs to the package. |
I will investigate which dependencies are already incorporated in the SDK and if necessary I will complete them. If I manage to have the logs in local tests I will place them here. |
Hi, I'm compiling version 1.24.11 along with the dependencies, the problem is that it doesn't finish compiling and I have no idea what the error is. Since I'm not sure which dependencies are already satisfied I've been completing them by trial and error. On arm and x64 different errors occur
The recipe for building the package in the following link
https://github.com/flathub/org.lyx.LyX.Plugin.SweaveKnitr/blob/bbbb/org.lyx.LyX.Plugin.SweaveKnitr.yml
and the compilation process with the errors in
https://buildbot.flathub.org/#/builders/6/builds/169906
Thanks for any clues about the problem.
The text was updated successfully, but these errors were encountered: