-
Notifications
You must be signed in to change notification settings - Fork 171
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
MacOS: fails to build extension #592
Comments
This is strange. Could you attach the generated
|
Yes. And it happens with another macro as well ( Here are the files. Oh, and it's with Xcode-14.2. |
@rhenium this is a consistent failure. Help would be appreciated. |
Do you have libcrypto*.dylib in According to this log output, conftest.c correctly found the 1.1.1 headers in This may be https://bugs.ruby-lang.org/issues/9760:
However I'm not sure why it would fail with OpenSSL 3.0.7, too (without specifying |
Re. (1): I don't know.
I do not know about (1).
Good question. Another good question would be - why, given that OpenSSL 3.0.7 is installed symlinked to |
It looks like How can I test to make sure the correct/latest gem and extension are installed and set to default? |
Any updates here? |
Same problem here |
I noticed a quirk that may shed light on the problem. My copy of Ruby believes itself to be using OpenSSL version 1.1, but the compilation of the gem is trying version 3 of OpenSSL. Might this version mismatch explain the incorrect version shim macro that @rhenium pointed out? Below is my error when compiling the gem per the instructions on the CONTRIBUTING page. Notice that the output contains references to
This output agrees with the version that the
But, this differs from the version my installation of Ruby thinks it is using. Ruby believes it is on version 1.1 of OpenSSL:
Indeed, I thought that Ruby did not support OpenSSL 3 until Ruby version 3.1 or later. I am using Ruby 3.0.4 in this example. So, it seems very wrong to me that my compilation of the openssl gem should create output related to version 3 of OpenSSL which my version of Ruby does not support. Is this configuration somehow jammed between versions of OpenSSL? Perhaps the code is querying the OpenSSL version in two different ways, returning two different results, which is then executing two incompatible parts of the code? In this issue, @BrianHawley believes configuration and compilation are picking two different versions when both the Setup: I am on an Intel Macbook, Sonoma 14.4, using Homebrew and Ruby 3.0.4p208 installed with RVM. |
I was able to manually install using:
Then I could |
With
Seems to have made the trick for me... |
MacOS Monterey 12.6.2 (Interl-based iMac), OpenSSL-1.1.1s (also have OpenSSL-3.0.7, but it fails to build extension exactly the same way), Macports-installed Ruby-3.2 (same results with Ruby-3.1).
The problem seems to be with
openssl-3.1.0/ext/openssl/openssl_missing.h
file, which improperly re-defines certain functions:Attempts to edit the offending file locally and recompile succeed - but the gem cannot be installed:
openssl-3.0.1
gem installs fine.The text was updated successfully, but these errors were encountered: