-
Notifications
You must be signed in to change notification settings - Fork 123
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
pycapnp version 0.5.12 ships capnp 0.5.3.1 but clang 4 / capnp::Kind still error #152
Comments
Can you attach the output of pip install -v or similar? |
Output of
This is on Ubuntu, in virtualenv, otherwise capnp is and has been working fine |
That looks like a successful install. What is the error you're seeing? |
|
It looks like you may be picking up an older version of pycapnp than you think? Can you get the nupic install to do a verbose build and check versions in the output? |
Thank you! You're correct, for some reason we ship the tarball and it was at the 0.5.3(not .1) version. Should pycapnp enforce (check for) the exact capnp version it's supposed to run with? To avoid problems like this. |
It feels like this issue could be closed. |
Thank you for leading me through the debug process! 👍 |
I'm using the latest pycapnp release from pypi, which is 0.5.12. According to the changelog it ships capnp 0.5.3.1, which contains a fix for compilation with clang 4.x:
capnproto/capnproto#433
However, I'm still getting the same error that was supposed to be fixed. Is the problem in pycapnp, capnp, or somewhere else?
Thank you,
The text was updated successfully, but these errors were encountered: