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

clang compatibility fixes #3

Merged
merged 1 commit into from
Oct 25, 2019
Merged

clang compatibility fixes #3

merged 1 commit into from
Oct 25, 2019

Conversation

mieko
Copy link
Contributor

@mieko mieko commented Jul 29, 2016

The default value in the mkLit declaration (vs. definition) won't compile with modern clang. The other minor edits are warning fixes. This version of minisat is still current with upstream, but minisat PRs with a fix haven't gotten a response in a while.

Ref: niklasso/minisat#16, niklasso/minisat#22, niklasso/minisat#12, niklasso/minisat#27. Closes #1

@mieko
Copy link
Contributor Author

mieko commented Jul 29, 2016

@mame said in #1:

This issue should be fixed in the upstream of minisat. I have no thought of patching the bundled source of minisat.

This really should be fixed upstream, although there has been little response. I understand not wanting to carry around a patched copy, so I'll leave this branch around for anyone who needs it, assuming the PR is closed.

@alexrudall
Copy link

alexrudall commented Mar 22, 2017

mieko - thank you for leaving the branch, I have been able to use it successfully on OSX with the following in my Gemfile:

gem 'ruby-minisat', git: 'https://github.com/mieko/ruby-minisat', branch: 'clang-fixes'

Much appreciated!

@mame
Copy link
Owner

mame commented Oct 25, 2019

Sorry for my long absence. It is really unfortunate that minisat is not maintained. Now it fails to build on my machine 😢 , so I'll merge it. Thank you very much.

@mame mame merged commit 9d881be into mame:master Oct 25, 2019
@mieko
Copy link
Contributor Author

mieko commented Oct 25, 2019

@mame I just appreciate you putting it together. Thanks so much.

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.

Is the Shikaku solution correct?
3 participants