Trying to compile prusaslicer-2.4.2, fails on /var/tmp/portage/media-gfx/prusaslicer-2.4.2/work/PrusaSlicer-version_2.4.2/src/hints/HintsToPot.cpp: In function ‘bool write_to_pot(boost::filesystem::path, const std::vector<std::pair<std ::__cxx11::basic_string<char>, std::__cxx11::basic_string<char> > >&)’: /var/tmp/portage/media-gfx/prusaslicer-2.4.2/work/PrusaSlicer-version_2.4.2/src/hints/HintsToPot.cpp:12:21: error: ‘ofstream’ is not a member of ‘boost::filesystem’ 12 | boost::filesystem::ofstream file(std::move(path), std::ios_base::app); | ^~~~~~~~ Reproducible: Always Steps to Reproduce: 1.emerge =prusaslicer-2.4.2 2. 3. Actual Results: Compile error Expected Results: Should compile
1. Always include the full build.lo and emerge --info. 2. Why aren't you building 2.6.0_pre20220601 which fixes this?
Created attachment 787265 [details] build.log
Created attachment 787268 [details] emerge --info
(In reply to Sam James from comment #1) > 1. Always include the full build.lo and emerge --info. I was preparing to attach them, you went too fast :-) > 2. Why aren't you building 2.6.0_pre20220601 which fixes this? Because it crashes all over the place.
(In reply to xiaojie+bugzillagentoo from comment #4) > (In reply to Sam James from comment #1) > > 1. Always include the full build.lo and emerge --info. > > I was preparing to attach them, you went too fast :-) > > > 2. Why aren't you building 2.6.0_pre20220601 which fixes this? > > Because it crashes all over the place. Alright, fair enough. It might be a pain to try backport the fixes but they're trivial by themselves (just missing includes). I can try.
It is known that old version do not work with new boost, for that we have a snapshot in tree. I use it daily and it yet to crash on me. What are the steps to reproduce your crashes? The version 2.4.2 is to be dropped out of tree as a version that do not work with stable boost. Check if media-gfx/prusaslicer-2.6.0_pre20220620 works better for you.
(In reply to Sam James from comment #5) > (In reply to xiaojie+bugzillagentoo from comment #4) > > (In reply to Sam James from comment #1) > > > 1. Always include the full build.lo and emerge --info. > > > > I was preparing to attach them, you went too fast :-) > > > > > 2. Why aren't you building 2.6.0_pre20220601 which fixes this? > > > > Because it crashes all over the place. > > Alright, fair enough. It might be a pain to try backport the fixes but > they're trivial by themselves (just missing includes). I can try. Wait a few days, I'm gonna try 2.6.0 again.
Closin this bug since 2.4.2_p20220506 (which includes the proper patch for boost) does compile ok, and all following ebuilds too. This does not solve the slicer crashing, but I'll open a new bug report.
