-
-
Notifications
You must be signed in to change notification settings - Fork 749
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
Can't locate IPC/Cmd.pm in @INC with openssl v0.9.93 #2036
Comments
IIRC maturin runs the build in a manylinux Docker image. Installing dependencies in the host Ubuntu install will not make them available in the container. |
Ah ok, that would exain why my attempts have failed so far. Let me see if I
can add the perl installation to the maturin build, not quite sure how I'd
do that immediately.
Thanks for your quick reply
…On Wed, Sep 6, 2023, 20:13 Steven Fackler ***@***.***> wrote:
IIRC maturin runs the build in a manylinux Docker image. Installing
dependencies in the host Ubuntu install will not make them available in the
container.
—
Reply to this email directly, view it on GitHub
<#2036 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABEZV2ABL5JMVEX6XH6KM5TXZEUVZANCNFSM6AAAAAA4OE6JH4>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
For those who encounter this issue, remove the So I'm not quite sure what was going on: it's either some cache that wasn't invalidated when it should have, or something with the Thanks sfackler for pointing me toward the right directly. Successful build here. |
@ChristopherRabotin. Disabling 'manylinux: auto' would make your package uninstallable on old systems. So, the actual problem is that if you use You can find list of all containers that runs for specific targets in maturin-action's README here (Note that x86 containers are spelled as i686). Interesting thing here is that some containers are debian-based, and others are RHEL-based. So you cannot simply put I was struggling wit this problem for days. You solution initially helped to fast-release the package, but then I couldn't install it inside my docker-containers, so I was trying to find another one. You can see the working workflow here: https://github.com/Intreecom/scyllapy/blob/develop/.github/workflows/release.yaml Also I depend on libatomic, and I'm not sure if it's for openssl. But if you find any problems linking with |
@s3rius A thousand thanks! I encountered this issue again just this week and my previous fix no longer worked, but yours does! Thank you, thank you, thank you! |
@s3rius - THANK YOU! I spent about 2 hours trying to debug an openssl issue until I stumbled across your solution. Works perfectly. |
taking into account CentOS vs. Debian-based manylinux images. Solution taken from: sfackler/rust-openssl#2036 (comment)
Until version 0.9.93, openssl would build perfectly fine in a Github workflow without additional dependencies. This is no longer the case since v0.9.93.
I've tried at least five different packages to install in the ubuntu-latest Github workflow, as evidenced here, and still openssl fails to build.
This is obviously related to #1550, but the answer is stunningly vague as to which "required perl packages" should be installed.
I suspect that this is as simple as installing the correct packages. The following are not the ones to install:
I appreciate if someone could quickly answer since I've been headbutting on this for a short while now and have lost all hope in figure out what Perl package is needed (and also wonder why Perl hasn't died yet, but that's another conversation).
The text was updated successfully, but these errors were encountered: