-
Notifications
You must be signed in to change notification settings - Fork 747
ring 0.17.13 does not "cross" compile (on illumos, other x86_64 targets) unlike ring 0.17.12 #2461
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
Comments
What version of binutils are you using? If you google that error message, people claim that upgrading to 2.38 helps. |
we met the same error too. ring = "0.17.13" , this version caused the error. |
error log: [email protected]: ToolExecError: command did not execute successfully (status code exit status: 1): LC_ALL="C" "cc" "-O3" "-ffunction-sections" "-fdata-sections" "-fPIC" "-m64" "-I" "/cargo/registry/src/index.crates.io-1949cf8c6b5b557f/ring-0.17.13/include" "-I" "/cargo/registry/src/index.crates.io-1949cf8c6b5b557f/ring-0.17.13/pregenerated" "-Wall" "-Wextra" "-fvisibility=hidden" "-std=c1x" "-Wall" "-Wbad-function-cast" "-Wcast-align" "-Wcast-qual" "-Wconversion" "-Wmissing-field-initializers" "-Wmissing-include-dirs" "-Wnested-externs" "-Wredundant-decls" "-Wshadow" "-Wsign-compare" "-Wsign-conversion" "-Wstrict-prototypes" "-Wundef" "-Wuninitialized" "-g3" "-DNDEBUG" "-o" "/target/x86_64-unknown-linux-gnu/release/build/ring-4503903eec66e078/out/c322a0bcc369f531-aes-gcm-avx2-x86_64-elf.o" "-c" "/cargo/registry/src/index.crates.io-1949cf8c6b5b557f/ring-0.17.13/pregenerated/aes-gcm-avx2-x86_64-elf.S" error: failed to run custom build command for |
On my system I have:
Please report what you have. |
Also, you can use 0.17.12 which doesn't have any increased |
I am actually using cross-rs to compile it for illumos. I think we have to pin ring to 0.17.12 on illumos (and file an issue at cross-rs/cross to update assembler) EDIT: cross-rs/cross seems to be on Ubuntu 20.04 and uses binutils 2.28.1 |
me too. error occurred in cc-rs: command did not execute successfully (status code exit status: 1): LC_ALL="C" "cc" "-O0" "-ffunction-sections" "-fdata-sections" "-fPIC" "-gdwarf-4" "-fno-omit-frame-pointer" "-m64" "-I" "/cargo/registry/src/index.crates.io-1949cf8c6b5b557f/ring-0.17.13/include" "-I" "/cargo/registry/src/index.crates.io-1949cf8c6b5b557f/ring-0.17.13/pregenerated" "-Wall" "-Wextra" "-fvisibility=hidden" "-std=c1x" "-Wall" "-Wbad-function-cast" "-Wcast-align" "-Wcast-qual" "-Wconversion" "-Wmissing-field-initializers" "-Wmissing-include-dirs" "-Wnested-externs" "-Wredundant-decls" "-Wshadow" "-Wsign-compare" "-Wsign-conversion" "-Wstrict-prototypes" "-Wundef" "-Wuninitialized" "-g3" "-DNDEBUG" "-o" "/target/x86_64-unknown-linux-gnu/debug/build/ring-fb03db282ef36793/out/c322a0bcc369f531-aes-gcm-avx2-x86_64-elf.o" "-c" "/cargo/registry/src/index.crates.io-1949cf8c6b5b557f/ring-0.17.13/pregenerated/aes-gcm-avx2-x86_64-elf.S" |
Downgrading to ring 0.17.12 is a short-term workaround but it won't work in the long term, so it is good to find solutions. It is good that people are working to upgrade binutils in cross-rs. If there are other situations where this is an issue, then knowing the host operating system version (e.g. Ubuntu 20.04, RHEL 7, etc.) and the |
According to the log above, these (using XMM registers) are accepted by the assembler:
But these are not:
So the issue is that the old |
I verified with https://github.com/briansmith/ring/actions/runs/13724945792/job/38389040003 that the x86-64 build works fine in Ubuntu 20.04 in GitHub Actions, and that's the oldest Ubuntu in GitHub Actions, AFAICT. So maybe upgrading binutils in cross may be the only thing we need to do. |
It seems this will be fixed in cross-rs: cross-rs/cross#1639. I'm going to close this now. |
In #2462 (comment), @azjezz wrote:
|
0.17.14 was released with the fix for this. |
ring 0.17.11 used to compile perfectly in rust (+nightly-2025-01-25) but after updating to ring 0.17.13, it fails to compile
The text was updated successfully, but these errors were encountered: