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: | 14 |
Popularity: | 0.000024 |
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-rocm-gitAUR, llvm-gitAUR, clang-minimal-gitAUR, clang17-binAUR) (make)
- cmake (cmake-gitAUR) (make)
- eigen (eigen-gitAUR) (make)
- git (git-gitAUR, git-glAUR) (make)
- gtest (googletest-gitAUR) (make)
- ninja (ninja-kitwareAUR, ninja-memAUR, ninja-fuchsia-gitAUR, ninja-gitAUR, ninja-jobserverAUR) (make)
Latest Comments
« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 .. 15 Next › Last »
ArchBoxHero commented on 2022-02-25 17:12 (UTC) (edited on 2022-02-25 17:17 (UTC) by ArchBoxHero)
I can confirm the same fail on another Arch Linux system as well as my main. Same exact errors as @DCengineer.
DCengineer commented on 2022-02-23 03:23 (UTC) (edited on 2022-02-23 03:23 (UTC) by DCengineer)
@Salamandar Well, that didn't take long. It built perfectly for a day. Now the patches are failing.
ArchBoxHero commented on 2022-02-22 01:06 (UTC) (edited on 2022-02-22 01:08 (UTC) by ArchBoxHero)
Snap Crackle POP! It builds. Thanks @Salamandar. Nice. And Ninja doesn't crash my system. It now takes up around 43% of 64G-RAM and pushes my cores while linking but does what it should be doing. Little new with the Ninja build system. I know a little bout how it works with Cmake and what not but not enough.
Salamandar commented on 2022-02-21 10:48 (UTC)
The build / RAM issues shouldn't occur anymore, as the package now uses Clang to build.
ArchBoxHero commented on 2022-02-11 06:17 (UTC) (edited on 2022-02-11 17:06 (UTC) by ArchBoxHero)
Hey I am wondering if anyone else is having this issue while trying to build this package(I cannot build it). I've tried it on 2 machines and get the same result when building:
Its when the build gets to here:
It literally pushes my CPU 100% and maxes out my ram on both systems and if I don't exit out fast enough it will crash.
In the PKBUILD there's this trick:
which I thought would avoid the RAM issue? I'm not familiar with ninja enough but I'll poke around now.
*I was able to get it to build without consuming all those resources adjusting those ninja build commands like this:
Of course took some time(still building 10minutes later). Funny 32cores and 64GB-RAM and I am moving at a snails pace to build this. I'm sure I could have tinkered and adjusted it but this was fine for it to just build. I'm having some RAM issues with this prusa in general software since the last update. Hoping this might stop the slicer from crashing while taking all the RAM and crunching the CPU at 100%. No Idea what's going on with prusa libs.
Yea it fails here now:
I don't see anyone else with this
I found that using this command
lets it build without crashing the RAM in place of the and Lat thing, the build fails on my system running Arch.seanahan commented on 2022-02-06 23:17 (UTC)
I'm not sure what causes this, but
git describe --tags
does not necessarily return the correct, latest tagged version. Currently, it returnsversion_2.4.0-beta4-487-gb88fc2896
; however, the actual latest tag isversion_2.4.1-beta1
. (I think it's is an oddity with git itself.) This can cause Pacman to think incorrectly that the package freshly built off of the tip of master is a downgrade because the version number is using an older release as it's reference point.One option might be to use
git tag --sort=-taggerdate | head -n 1
. The-
beforetaggerdate
tellsgit-sort
to reverse the sort order.Here's a quick patch I hacked up:
Salamandar commented on 2022-01-26 15:13 (UTC)
In the future you can check if the latest pkgbuild builds here : https://gitlab.com/Salamandar/aur_packages/-/pipelines/
sam_agasse commented on 2022-01-26 13:38 (UTC)
@dflemstr, @Salamandar : I confirm, downgrading fixes also the issue for me. Thanks to all for your support, I can now enjoy 3D printing ;-)
Salamandar commented on 2022-01-26 12:40 (UTC)
Alright, I can reproduce with the latest cereal package. This is already reported upstream : https://github.com/prusa3d/PrusaSlicer/pull/7809
I can't get my head around cereal completely changing their packaging/building process with a micro version change…
dflemstr commented on 2022-01-25 20:31 (UTC)
The package only fails to build with latest cereal (
cereal-1.3.1-1
)Downgrading to
cereal-1.3.0-1
lets me build the package again.« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 .. 15 Next › Last »