-
-
Notifications
You must be signed in to change notification settings - Fork 9.9k
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
Build OpenSSL on ubuntu, compile failed in x86_32(providers/legacy.so) #11281
Comments
For x86-32, this is the config what we are using: "linux32 ./config -g3 -Werror no-deprecated --prefix=/home/ent-user/work/ci-scripts/openssl-install", with this configuration, then "make" openssl for x86-32 compiled failure. But strangely, once we remove the option "
", it can compile successfully. |
What is that "linux32"? |
This option "linux32" to make the code detect the arch of 32 bit. Before, we simply try -m32, but found many errors during compile, the linux32 can make it compile successfully. |
Could you please do this, so I can see what the actual configuration is, in terms I understand? Short version:
Long version:
|
---Short version result as below:
Long version result as below:
|
Ok, thanks. From my testing, it seems that
|
Maybe I compiled it with multi threads, the log be flooded... |
If I build it with simple command "make", I can get the same error report with you.@levitte |
No need at this point, I'm doing the same build and can confirm your report |
Having looked and compared a build with and without |
I'll try and adjust crypto/build.info to make this work the way it should |
Please try with #11311, and see if that makes things work a bit better. It does on my machine... |
With PR #11311, it also works on my local, thanks for the fix. |
We were using CPUID coded in several modules, but it was unclear how it actually got there, and could fail randomly. To remedy that, this change separates the CPUID C code from the rest of cryptlib.c, and ensures the right modules get both that and the assembler sources explicitly. Fixes openssl#11281
I verified it locally with the openssl master branch commit: daa86f9. Seems the issue has been gone. |
The install targets don't lend themselves well for parallelism. This is known, and yet unresolved. Different issue, though. |
Thanks. Closing |
We were using CPUID coded in several modules, but it was unclear how it actually got there, and could fail randomly. To remedy that, this change separates the CPUID C code from the rest of cryptlib.c, and ensures the right modules get both that and the assembler sources explicitly. Fixes openssl#11281
We were using CPUID coded in several modules, but it was unclear how it actually got there, and could fail randomly. To remedy that, this change separates the CPUID C code from the rest of cryptlib.c, and ensures the right modules get both that and the assembler sources explicitly. Fixes #11281 Reviewed-by: Tomas Mraz <tomas@openssl.org> (Merged from #14755)
Get the latest OpenSSL code of master branch, "./config; make; make install_sw;". compile it on ubuntu. find that the builds on x86-64,aarch32,aarch64 are success but fails on x86-32. The error log as below:
The text was updated successfully, but these errors were encountered: