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

libcrypto not properly picked up in binary wheel #72

Closed
gijzelaerr opened this issue Jul 4, 2020 · 6 comments
Closed

libcrypto not properly picked up in binary wheel #72

gijzelaerr opened this issue Jul 4, 2020 · 6 comments
Assignees
Labels
bug Something isn't working
Milestone

Comments

@gijzelaerr
Copy link
Collaborator

gijzelaerr commented Jul 4, 2020

Monetdbe requires libcrypto from openssl. Somewhere the binary wheel construction tools don't pick up this dependency.

This changed, since as far as I know with the monetdbe C code bundled with previous releases didn't have a hard dependency on openssl.

This might be related to the comment in the pep spec:

https://www.python.org/dev/peps/pep-0513/#the-manylinux1-policy

"libcrypt.so.1 was retrospectively removed from the whitelist after Fedora 30 was released with libcrypt.so.2 instead."

@gijzelaerr gijzelaerr self-assigned this Jul 4, 2020
@gijzelaerr gijzelaerr added the bug Something isn't working label Jul 4, 2020
@gijzelaerr gijzelaerr added this to the 0.9 milestone Jul 4, 2020
@njnes
Copy link
Member

njnes commented Jul 4, 2020

I'm sure this changed because of the authentication code now being used during startup. This is strictly speaking not needed, but given furture plans which may involve users authenticating, we should keep this.

@gijzelaerr
Copy link
Collaborator Author

a workaround, for now, could be to disable this so the binary wheel works while we find a solution to this problem?

@ghost
Copy link

ghost commented Jul 4, 2020

I would opt for temporarily disabling it, because the first release should not fall flat on its face due to future requirements

@njnes
Copy link
Member

njnes commented Jul 4, 2020

I've added a cmake option for this.
-DWITH_CRYPTO=OFF should do the trick now.

@gijzelaerr gijzelaerr modified the milestones: 0.9, 0.8.1 Jul 4, 2020
@gijzelaerr
Copy link
Collaborator Author

ill build and push a new release with this flag disabled in a bit. Are there no other issues that require love for 0.8.1?

@gijzelaerr
Copy link
Collaborator Author

0.8.1 pushed to pypi for Linux, OSX build fails.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants