scipopt / papilo

Parallel Presolve for Integer and Linear Optimization
GNU Lesser General Public License v3.0
64 stars 17 forks source link

build failure on fedora-37 #23

Closed mkoeppe closed 1 year ago

mkoeppe commented 2 years ago
  [papilo-2.1.1]                    from /sage/local/var/tmp/sage/build/papilo-2.1.1/src/src/papilo/io/MpsParser.hpp:28,
  [papilo-2.1.1]                    from /sage/local/var/tmp/sage/build/papilo-2.1.1/src/test/papilo/io/MpsParserTest.cpp:24:
  [papilo-2.1.1]   /usr/include/boost/multiprecision/float128.hpp: In member function 'std::string boost::multiprecision::backends::float128_backend::str(std::streamsize, std::ios_base::fmtflags) const':
  [papilo-2.1.1]   /usr/include/boost/multiprecision/float128.hpp:260:15: error: 'unique_ptr' is not a member of 'std'
  [papilo-2.1.1]     260 |          std::unique_ptr<char[]>   buf2;
  [papilo-2.1.1]         |               ^~~~~~~~~~
  [papilo-2.1.1]   /usr/include/boost/multiprecision/float128.hpp:12:1: note: 'std::unique_ptr' is defined in header '<memory>'; did you forget to '#include <memory>'?

https://github.com/mkoeppe/PySCIPOpt/actions/runs/3506612801/jobs/5873771362

dimpase commented 2 years ago

missing #include <memory> somewhere?

alexhoen commented 2 years ago

yes I added a #include #memory on the master branch. Could you please restart the pipeline to see if works?

mkoeppe commented 2 years ago

Running at https://github.com/mkoeppe/PySCIPOpt/actions/runs/3506612801/jobs/5917100317

mkoeppe commented 2 years ago

This helped, but the next error:

  [papilo-2.1.1]                    from /sage/local/var/tmp/sage/build/papilo-2.1.1/src/src/papilo/core/ProbingView.cpp:24:
  [papilo-2.1.1]   /usr/include/boost/multiprecision/float128.hpp: In member function 'std::string boost::multiprecision::backends::float128_backend::str(std::streamsize, std::ios_base::fmtflags) const':
  [papilo-2.1.1]   /usr/include/boost/multiprecision/float128.hpp:260:15: error: 'unique_ptr' is not a member of 'std'

So the new #include should probably be moved to some header file instead.

mkoeppe commented 2 years ago

By the way, you can inspect the failing build by using docker run -it ghcr.io/mkoeppe/pyscipopt/pyscipoptsage-docker-fedora-37-standard-with-targets:9.8.beta4-49-ged0ebdd438-dirty-failed bash