Open nagisa opened 5 years ago
Once I cloned the index manually
git clone https://github.com/rust-lang/crates.io-index ~/.cargo/registry/index/github.com-eae4ba8cbf2ce1c7
it now works well.
@nagisa I can work around this problem by building cargo
from source. For me, it affects only Debian's cargo
package. Once I built cargo
from source and placed it into my path, the problem goes away.
CC @jrtc27
I made an interesting observation, the problem does not show up when running cargo
as root.
It also does not show when switching to my user from root without a login shell:
root@gcc202:~# su glaubitz
glaubitz@gcc202:/root$ cd
glaubitz@gcc202:~$ cd rust
glaubitz@gcc202:~/rust$ ./x.py build
Updating only changed submodules
Submodules updated in 0.06 seconds
Updating crates.io index
^C
Build completed unsuccessfully in 0:00:02
glaubitz@gcc202:~/rust$ exit
root@gcc202:~# su - glaubitz
glaubitz@gcc202:~$ cd rust
glaubitz@gcc202:~/rust$ ./x.py build
Updating only changed submodules
Submodules updated in 0.06 seconds
Updating crates.io index
error: failed to fetch `https://github.com/rust-lang/crates.io-index`
Caused by:
the SSL certificate is invalid: 0x08 - The certificate is not correctly signed by the trusted CA; class=Ssl (16); code=Certificate (-17)
failed to run: /usr/bin/cargo build --manifest-path /home/glaubitz/rust/src/bootstrap/Cargo.toml
Build completed unsuccessfully in 0:00:00
glaubitz@gcc202:~/rust$ logout
root@gcc202:~#
And, on top of that, it doesn't show on a second Linux/sparc64 porterbox. Could be a configuration after all.
Problem
It appears that there might be some bug in how cargo does its certificate validation on sparc64. It possibly may extend to other big-endian systems as well, but I haven’t been able to verify it (on both mips64 and ppc64 things I have access to the glibc is too old for rustup).
Steps
build
a rust library for the first time)Possible Solution(s)
Notes