Package Details: prusa-slicer-git 2.6.0.beta4.r1.gdbc2584d8-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 (RepRap, Makerbot, Ultimaker etc.)
Upstream URL: https://github.com/prusa3d/PrusaSlicer
Licenses: AGPL3
Conflicts: prusa-slicer
Submitter: Salamandar
Maintainer: Salamandar
Last Packager: Salamandar
Votes: 14
Popularity: 1.10
First Submitted: 2019-07-08 08:14 (UTC)
Last Updated: 2023-06-07 09:34 (UTC)

Latest Comments

1 2 3 4 5 6 .. 15 Next › Last »

gyscos commented on 2023-06-03 22:07 (UTC) (edited on 2023-06-09 23:58 (UTC) by gyscos)

Current status as of RC-1:

All cherry picked commits have been merged, so just remove/comment any git cherry-pick line from the PKGBUILD.

The openSSL race-condition build failure is still there, and it's still random, so just retry if it fails once.

Previous update:

Current status as of beta 4:

Of the 3 cherry-picked commits, one was rebased (and is now 2c21a503b7861b6b993cc07f1433eb5a2d891a83), the other two have been merged.

So the 3 cherry-pick commands should be replaced with the single git cherry-pick 2c21a503b7861b6b993cc07f1433eb5a2d891a83. It currently builds fine with this.

jamincollins commented on 2023-05-31 19:51 (UTC)

Looks like SRCINFO didn't get updated.

Salamandar commented on 2023-05-31 19:37 (UTC)

FYI, build should be fixed now.

jamincollins commented on 2023-05-31 18:06 (UTC)

Rather than fighting with compiling the git version (there are now other issues than the three listed), I created a new package that will be updated for every release build published on GitHub: https://aur.archlinux.org/packages/prusa-slicer-rel-bin

gyscos commented on 2023-05-21 10:31 (UTC) (edited on 2023-05-21 10:43 (UTC) by gyscos)

There's 3 different issues affecting this package at the moment:

  • The current 0001-Fix-format-string.patch is outdated and should just be removed. You can remove the patch -p1 ... line from the prepare() step.
  • Until the linked PR (https://github.com/prusa3d/PrusaSlicer/pull/10499) has been merged (it hasn't yet at this time), it needs to be manually checked out (or applied via a new patch file) before attempting to build. I decided to apply it as a patch, so I don't need to rebase the branch on the latest master (and indeed the latest master has since moved forward).
  • Random race conditions during the vendored OpenSSL compilation lead to random build failures, but re-trying compilation can work eventually (it did for me). You might also try single-threaded build as others mentioned, but build will likely take forever (I haven't tried that).

For the first two fixes, here's a patch file that will update the PKGBUILD and local patch files: https://gist.github.com/gyscos/347bf2d62cf93eb8d6d8c0b93341c344

auditor_3d commented on 2023-05-19 19:07 (UTC)

@gyscos, so explain this to a layman. What is going on here? I am getting the same error. You sayin just keep trying to build it until it works?

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:

==> Starting prepare()...
patching file src/slic3r/GUI/ImGuiWrapper.cpp
Hunk #1 FAILED at 460.
1 out of 1 hunk FAILED -- saving rejects to file src/slic3r/GUI/ImGuiWrapper.cpp.rej
==> ERROR: A failure occurred in prepare().
    Aborting...

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 :

/home/felix/.cache/yay/prusa-slicer-git/src/deps/build/dep_OpenEXR-prefix/src/dep_OpenEXR/OpenEXR/IlmImf/ImfDwaCompressor.cpp:746:31: error: unknown type name 'uintptr_t'; did you mean 'intptr_t'?

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.

1 2 3 4 5 6 .. 15 Next › Last »