rust-openssl: set resolver="2" for workspacesilences an annoying warning
rust-openssl: switch from deprecated config to config.toml
Unbreak rust-openssl-tests on sparc64For the test compilation using the CC crate, base clang is good enough,so we don't need to pull in another heavy dependency just for this test.
zap weird spaces $EDITOR added in previous
skip rust-openssl-tests on sparc64The issue is likely that the build is trying to compile some generatedC code with the prehistoric gcc from base, so add a tentative workaroundfor that. Since I d
skip rust-openssl-tests on sparc64The issue is likely that the build is trying to compile some generatedC code with the prehistoric gcc from base, so add a tentative workaroundfor that. Since I don't currently have access to a sparc64 box where Icould validate this easily and check if the workaround is enough, let'snot waste lots of cycles on this.
show more ...
Provide a harness driving rust-openssl's regress testsrust-openssl is an integral part of the Rust ecosystem and more than adozen ports, including lang/rust itself, depend on it. We need to ensure
Provide a harness driving rust-openssl's regress testsrust-openssl is an integral part of the Rust ecosystem and more than adozen ports, including lang/rust itself, depend on it. We need to ensurethat it keeps working with LibreSSL.If the rust and rust-openssl-tests packages are installed, create a cargoworkspace under obj/ that compiles and runs the rust-openssl regress testsmuch like what is done for the openssl-ruby tests. This expands our regresscoverage: for instance, this would have caught the broken ASN.1 indefinitelength encoding caused by asn1/tasn_enc.c r1.25.Positive feedback beck jsing semarieTesting and ok anton