Skip to content
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

Update to GLPK 4.65 #28

Closed
wants to merge 2 commits into from
Closed

Conversation

MisterDA
Copy link
Contributor

GLPK 4.65 was released on Thu Feb 16 10:00:00 2018, and is present in Debian Buster (stable).

@MisterDA MisterDA force-pushed the glpk-4.65 branch 4 times, most recently from 79385c9 to a87fced Compare March 16, 2020 12:10
GLPK has a slightly daft way of identifying MSVC-specific blocks of code,
in that its nmake files define __WOE__ explicitly, rather than just using
the MSVC_specific _MSC_VER define (note that mingw-w64 builds do *not*
define __WOE__).

This commit reapplies 2d05aca on top
of the GLPK 4.65 update.
@dra27
Copy link
Member

dra27 commented Jan 22, 2021

Is the second commit (changing the sources) strictly required? When vendoring, it's better to keep the patches only to the ones which must happen.

@dra27
Copy link
Member

dra27 commented Jan 22, 2021

GLPK 5.0 was released in December, so we should try to do that as well

@MisterDA
Copy link
Contributor Author

I don't remember... I was irritated by the CI failing and it appeared it didn't really need the glpk update for what I was working on at the time. Updating GLPK seems the best option.

@AltGr
Copy link
Collaborator

AltGr commented Feb 23, 2021

Thanks a lot! I just integrated this (manually) into master ; On a test case I get more than x2 steedup on opam resolution !

@AltGr AltGr closed this Feb 23, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants