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

fix unix boost version to 1.65.1 #66

Closed
wants to merge 1 commit into from
Closed

fix unix boost version to 1.65.1 #66

wants to merge 1 commit into from

Conversation

markussitzmann
Copy link

fix unix boost version to 1.65.1 in boost/meta.yaml

Copy link
Member

@greglandrum greglandrum left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don’t think this is required since we aren’t building boost for Linux anymore.
Was there a particular problem that lead to this?

@markussitzmann
Copy link
Author

The following of my Docker scripts (if you replace line 45-47 with 'rdkit/conda-rdkit' instead of my fork and checkout branch 'development'):

https://github.com/chembience/chembience/blob/master/context/base/rdkit/Dockerfile

created a RDKit version that was missing boost 1.65.1 and there was only (I think) boost 1.63 available. So, with my fork and the pushed fix I got it working again). Maybe I have to re-check it.

@greglandrum
Copy link
Member

Please give it a try again. Note that there were some fairly major changes to the way the build is done when we switched to the new anaconda5 setup with #64
This docker image shows a build process that works for me:
https://github.com/rdkit/rdkit_containers/blob/master/docker/centos6_anaconda5/Dockerfile

(I'm currently running that again now to confirm that it still works, I will update this comment if it does not).

@greglandrum
Copy link
Member

@markussitzmann : does the new version of the development branch work for you now?

@markussitzmann
Copy link
Author

markussitzmann commented Aug 5, 2018

Hi Greg,
sorry for the late reply - I had it working since then, however, the reason why I found your reply now is because I have trouble again with boost. I am currently investigating (I saw there are also some other recent issues with boost).

Markus

P.S. I think I have the boost pin problem like in #71 #72

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.

2 participants