Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 945022 - media-gfx/superslicer-2.5.59.10-r1 fails to compile: PhysicalPrinterDialog.cpp:567:27: error: call of overloaded ‘set_values(<brace-enclosed initializer list>)’ is ambiguous
Summary: media-gfx/superslicer-2.5.59.10-r1 fails to compile: PhysicalPrinterDialog.cp...
Status: UNCONFIRMED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal
Assignee: 3D Printing Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-11-26 08:43 UTC by Robert G. Siebeck
Modified: 2024-12-23 06:52 UTC (History)
4 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
build.log (build.log.bz2,67.37 KB, application/x-bzip2)
2024-11-26 08:44 UTC, Robert G. Siebeck
Details
emerge --info (emerge-info.txt,7.66 KB, text/plain)
2024-11-26 08:44 UTC, Robert G. Siebeck
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Robert G. Siebeck 2024-11-26 08:43:37 UTC
media-gfx/superslicer-2.5.59.10-r1 fails to compile

> /var/tmp/portage/media-gfx/superslicer-2.5.59.10-r1/work/SuperSlicer-2.5.59.10/src/slic3r/GUI/PhysicalPrinterDialog.cpp: In member function ‘void Slic3r::GUI::PhysicalPrinterDialog::build_printhost_settings(Slic3r::GUI::ConfigOptionsGroup*)’:
> /var/tmp/portage/media-gfx/superslicer-2.5.59.10-r1/work/SuperSlicer-2.5.59.10/src/slic3r/GUI/PhysicalPrinterDialog.cpp:567:27: error: call of overloaded ‘set_values(<brace-enclosed initializer list>)’ is ambiguous
> FAILED: src/slic3r/CMakeFiles/libslic3r_gui.dir/GUI/PhysicalPrinterDialog.cpp.o

Please find build.log and emerge --info attached.

Reproducible: Always
Comment 1 Robert G. Siebeck 2024-11-26 08:44:07 UTC
Created attachment 911973 [details]
build.log
Comment 2 Robert G. Siebeck 2024-11-26 08:44:26 UTC
Created attachment 911974 [details]
emerge --info
Comment 3 Niklaus 'vimja' Hofer 2024-12-08 22:22:35 UTC
I can confirm this is an issue. I'm having the same problem building Superslicer 2.5.59.10-r1.

Here is my build log: https://git.chaostreffbern.ch/-/snippets/1211

And here my emerge info: https://git.chaostreffbern.ch/-/snippets/1210
Comment 4 benland100 2024-12-20 20:01:28 UTC
Same issues as reported by other users; the in-repo superslicer versions do not build. I would estimate this has persisted for at least 4 months.

I've been attempting to maintain patches for superslicer for some time now to keep my system building, but this is an entirely futile effort as every single opencascade or boost update breaks something, and the issues go unfixed for months. My ebuild and patches are here if they are useful to anyone https://github.com/BenLand100/blandtoo/blob/master/media-gfx/superslicer/superslicer-2.5.60.0.ebuild --- but be warned, it broke again last week and I have not had time to fix it.
Comment 5 Sam James archtester Gentoo Infrastructure gentoo-dev Security 2024-12-22 00:41:37 UTC
Note that very few other Linux distributions package superslicer for this reason. It's hard to keep up with and upstream don't seem to test latest versions of deps in CI. If other distros do package it, they seem to often use a binary.
Comment 6 benland100 2024-12-22 19:52:28 UTC
Since the official ebuild is attempting to build SuperSlicer against package versions it was never tested with, including removing version constraints to allow this, I've opted to simply go the binary route instead of simply letting it linger. Here is the ebuild: https://github.com/BenLand100/blandtoo/blob/master/media-gfx/superslicer-bin/superslicer-bin-2.5.59.13.ebuild
Comment 7 Sam James archtester Gentoo Infrastructure gentoo-dev Security 2024-12-23 06:52:20 UTC
(In reply to benland100 from comment #6)
> Since the official ebuild is attempting to build SuperSlicer against package
> versions it was never tested with, including removing version constraints to
> allow this,

That's one component and not the one which usually breaks, even. But yes, we often have to do that (not least to avoid dep conflicts for users).