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

boost 1.60 fails building with no matching function for call to 'registry_lookup2' #1299

Closed
svenstaro opened this issue Dec 22, 2015 · 8 comments · Fixed by #1300
Closed

Comments

@svenstaro
Copy link

Arch Linux, gcc 5.3, boost 1.60. Compiles fine when disabling Python.

Build log: http://b.1339.cf/apfwyxv.log

@lgritz
Copy link
Collaborator

lgritz commented Dec 22, 2015

I looked at the log, and it's not an error I've seen before. Something is confusing Boost.Python.

Which OS and flavor is this?

Does it work on that platform for Boost 1.59?

Does it work with Boost 1.60 if you compile for C++11?

@svenstaro
Copy link
Author

Yes, works with 1.59. No, does not work for C++11. It's specifically a boost.python issue with 1.60. For OS and stuff, see above.

@lgritz
Copy link
Collaborator

lgritz commented Dec 23, 2015

I'll try downloading Boost 1.60 (which was just released a couple days ago) and see if I can reproduce on my end.

@lgritz
Copy link
Collaborator

lgritz commented Dec 23, 2015

The weird thing is that the Boost 1.60 release notes don't mention anything has changed with Boost.Python.

@lgritz
Copy link
Collaborator

lgritz commented Dec 23, 2015

The good (?) news is that I am able to reproduce this with boost 1.60 on my machine. So hang on, will work on this tomorrow.

@lgritz
Copy link
Collaborator

lgritz commented Dec 24, 2015

Fix proposed in #1300.

@david-geiger
Copy link

Hi,

I confirm that with the proposed fix openimageio-1.6.8 built fine now against boost 1.60.0 on Mageia Cauldron.

So, is it possible to fix 1.5 branch too?

Regards,
David

@lgritz
Copy link
Collaborator

lgritz commented Dec 28, 2015

I can't backport this to 1.5, it's too big a change (and compatibility break) for a stable release (let alone an obsolete one), but I can just disable the particular Python binding calls for ImageCache that don't compile correctly (they wouldn't have worked right anyway, so I think we can live with disabling them).

I'll push these fixes to master, RB-1.6, and RB-1.5 today.

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 a pull request may close this issue.

3 participants