Package Details: prusa-slicer-git 2.7.4-1

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)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 11 .. 15 Next › Last »

sam_agasse commented on 2022-01-25 12:24 (UTC)

Issue also happens with when I build Prusa-Slicer from https://archlinux.org/packages/community/x86_64/prusa-slicer/ [ 83%] Linking CXX executable prusa-slicer /usr/bin/ld: cannot find -lcereal /usr/bin/ld: cannot find -lcereal collect2: error: ld returned 1 exit status

sam_agasse commented on 2022-01-25 08:55 (UTC)

@Salamandar I have build bftrace which also depends on cereal. This worked fine. (makedepends=('cmake' 'llvm' 'git' 'linux-headers' 'ninja' 'gtest' 'cereal' 'asciidoctor' 'xxd')

Question from my side: Is this the right place to discuss this level of detail?

sam_agasse commented on 2022-01-25 08:25 (UTC) (edited on 2022-01-25 08:34 (UTC) by sam_agasse)

@Salamandar Thanks for your fast reply and support. I tried also with SuperSlicer as it has similar dependencies, same issue. I conclude that the problem is on my side, nevertheless I would appreciate your feedback with your test on a docker container. I tried to reinstall cereal, no change. Next I'look for another package that uses cereal and test.

Salamandar commented on 2022-01-24 19:16 (UTC)

@sam_agasse sorry, can't reproduce :( I'll try to spin an arch docker container to check.

Salamandar commented on 2022-01-24 18:38 (UTC)

@0x4242 @NomAnor The idea was to build first as fast as possible (like -j$(nproc)), and not stop on errors. And then run a second time with -j2 to be sure the build ran to the end.

The second call will just rebuild but do noting because everything is already built (if your ram can handle it).

I don't understand this statement. The second call will build what has not been built the first time.

That being said, I understand that's far from an ideal solution.

I'm thinking to force using clang to build this package. There's no ram issue with this compiler.

sam_agasse commented on 2022-01-24 18:29 (UTC) (edited on 2022-01-24 18:46 (UTC) by sam_agasse)

Tried today to build, but getting error "/usr/bin/ld: cannot find -lcereal". Package cereal from community is installed, system is up to date as per today. Any idea?

0x4242 commented on 2022-01-16 14:24 (UTC)

I can confirm @NomAnor's finding. Changing to ninja -k0 -j2 and deleting the 2nd call fixes the issue. I ended up using -j6. -j8 wouldn't work with 16GB RAM on my machine.

NomAnor commented on 2022-01-11 18:40 (UTC)

The fix for the gcc ram issue will not work. ninja is called twice and the first call (-k0) will just build everything with the default number of threads (all of them). The second call will just rebuild but do noting because everything is already built (if your ram can handle it).

I had to remove the second call and add the -j option to the first call. Can this be delegated to makepkg.conf similar to MAKEFLAGS='-j4'?

strangebrew commented on 2021-11-27 12:17 (UTC)

I ammended your patch to compile beta2: https://www.toptal.com/developers/hastebin/elubacofoc.cpp