> A native build of cura-engine on unstable amd64 ends with:
>
> | In file included from /usr/include/gtest/gtest.h:387,
> | from /<<PKGBUILDDIR>>/tests/utils/SparseGridTest.cpp:4:
> | /<<PKGBUILDDIR>>/tests/utils/SparseGridTest.cpp: In member function
> ‘virtual void cura::GetNearbyTest_GetNearby_Test::TestBody()’:
> | /<<PKGBUILDDIR>>/tests/utils/SparseGridTest.cpp:48:38: error: ‘find_if’ is
> not a member of ‘std’; did you mean ‘find’?
> | 48 | EXPECT_NE(result.end(), std::find_if(result.begin(),
> result.end(), [&point](const typename SparsePointGridInclusive<Point>::Elem
> &elem) { return elem.val == point; }))
> | | ^~~~~~~
This has been fixed upstream:
https://github.com/Ultimaker/CuraEngine/issues/1318
> This must be a very recent issue as neither crossqa (10 days ago) nor
> reproducible builds (6 days ago) have run into this issue. It's reliably
> reproducible anyhow. I'm unsure what might cause it. Neither gcc-10 nor
> cura-engine were uploaded in that time. It would be a good idea to add
> the missing #include <algorithm> any how.
Not sure, perhaps it was a change in one of the dependent libraries
(such as gtest).
Anyway, the fix should be in the next CuraEngine release (4.8), but we
can adopt the trivial patch from here in the meantime:
https://github.com/Ultimaker/CuraEngine/commit/ae354d80b25d90576f37222b6500f0e7ac45405b
