-
Notifications
You must be signed in to change notification settings - Fork 63
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for FreeBSD (amplmp compilation issue) #7
Comments
2min googling around: |
FYI: Issue still present in ampl/mp master https://github.com/ampl/mp/blob/master/src/os.cc#L107-L109 |
SCIP itself can be built on FreeBSD, see: |
@matbesancon thanks ! and shame on me I should have think of disabling AMPL support -_- Line 92 in 9444e80
on my way to test it... |
No problem :) |
IMHO: Could be closed since I did my duty and open an issue in the ampl repo. |
thank you, I'll open a corresponding issue on the main scip repo |
- supposed to bring FreeBSD support (#7) - should make #3284 unnecessary
When trying to build SCIP in our Vagrant generic/FreeBSD13 box (note a FreeBSD VirtualBox img) we are facing some compilation issue...
Observed
here the relevant trace (please notice we are building SCIP using FetchContent from our or-tools CMake based build)
ref: https://github.com/google/or-tools/runs/3672547012?check_suite_focus=true
scip/src/amplmp/src/os.cpp
Lines 107 to 109 in 9444e80
Expected
Have support of FreeBSD so we can use it in OR-Tools or at least a dummy function instead of this error message breaking the build ;)
Also it seems that amplmp is only use to read some .nl file so it's sad to break the build for this "optional" feature...
scip/src/amplmp/README
Line 2 in 9444e80
Annexe
You can found our Vagrantfile here: https://github.com/google/or-tools/blob/master/cmake/vagrant/freebsd/cpp/Vagrantfile
note: I think it should be easy to adapt it to only build SCIP starting from your repo to get rid of or-tools shenanigan and/or add it as a CI job to this repo (if you are willing to use github action workflow) ;)
The text was updated successfully, but these errors were encountered: