Search Criteria
Package Details: prusa-slicer-git 2.7.4-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/prusa-slicer-git.git (read-only, click to copy) |
---|---|
Package Base: | prusa-slicer-git |
Description: | G-code generator for 3D printers (Prusa fork of Slic3r) (git version) |
Upstream URL: | https://github.com/prusa3d/PrusaSlicer |
Licenses: | AGPL3 |
Conflicts: | prusa-slicer |
Submitter: | Salamandar |
Maintainer: | Salamandar |
Last Packager: | Salamandar |
Votes: | 15 |
Popularity: | 0.090416 |
First Submitted: | 2019-07-08 08:14 (UTC) |
Last Updated: | 2024-04-11 14:51 (UTC) |
Dependencies (8)
- dbus (dbus-gitAUR, dbus-selinuxAUR)
- intel-tbb (onetbb-gitAUR, onetbb)
- clang (llvm-gitAUR, clang-minimal-gitAUR, clang17-binAUR) (make)
- cmake (cmake3AUR, cmake-gitAUR) (make)
- eigen (eigen-gitAUR) (make)
- git (git-gitAUR, git-glAUR) (make)
- gtest (googletest-gitAUR) (make)
- ninja (ninja-kitwareAUR, ninja-fuchsia-gitAUR, ninja-gitAUR, ninja-jobserverAUR, ninja-memAUR, ninja-noemacs-gitAUR) (make)
Latest Comments
« First ‹ Previous 1 2 3 4 5 6 7 .. 15 Next › Last »
gyscos commented on 2023-05-16 13:51 (UTC) (edited on 2023-05-19 02:07 (UTC) by gyscos)
For me, this now fails applying the patch:
Essentially the patch is no longer required on the latest commits.
The remaining issues look fixed with https://github.com/prusa3d/PrusaSlicer/pull/10499
We could either take this PR as a patch, or checkout the branch directly.
The random failure when compiling OpenSSL is a bit annoying, but even on a 5900X (24 threads), it only affected me ~50% of the time, so re-running had a good chance of succeeding.
Salamandar commented on 2023-05-13 08:30 (UTC)
FYI this fails for me :
This is reported on other projects as well, and is due to the GCC 13 release: https://github.com/JuliaLang/julia/issues/49581
Not sure how I can handle that.
pavkamlc commented on 2023-05-13 07:59 (UTC)
I tried -j1, but build run a day and not finished on Ryzen5.
sippiecup commented on 2023-04-13 15:35 (UTC) (edited on 2023-04-13 15:36 (UTC) by sippiecup)
The OpenSSL error is a race condition when doing multithreaded builds. Thats why it looks random or why Salamandar is unable to easily replicate it. It seems to reliably fail once you get past 8 cores.
A temporary workaround is to just set the number of threads in /etc/makepkg.conf to 1, or forcing -j1 when building this package.
Hope this helps.
agalakhov commented on 2023-04-03 14:39 (UTC)
Can you please add 'git' to build dependencies? This is required for builds in clean environments where you can't assume Git to be installed even if the sources are pulled from Git.
ultraSsak commented on 2023-03-31 07:55 (UTC)
Same error as @edombek since like a month, Perhaps this started when Arch shipped new openSSL?
Thetic commented on 2023-03-31 04:49 (UTC)
I get the same error as @edombek. I tried 7 clean builds without success.
coffeevector commented on 2023-03-17 04:17 (UTC)
I am having the same error as @edombek. Clean building did not fix the issue.
Salamandar commented on 2023-03-12 10:41 (UTC) (edited on 2023-03-12 10:41 (UTC) by Salamandar)
@edombek this is a weird instability. It sometimes reproduces. Just re-run the build and it should run fine.
edombek commented on 2023-03-11 19:37 (UTC) (edited on 2023-03-11 20:00 (UTC) by edombek)
I get an error:
« First ‹ Previous 1 2 3 4 5 6 7 .. 15 Next › Last »