Open nguiard opened 3 years ago
I am also running into this. Adding -v
does nothing, to help debug, but looking at strace
output it appears that what's going on is that, unlike for crates from the registry, with git
sources it's not actually copying any files over from the git checkout into the vendor directory before it tries to create the .cargo-checksum.json
, which means that the target vendor directory doesn't exist yet.
So I'm actually not sure that this is cross-compilation related, it appears when vendoring
ar
at thex.py dist
step on a FreeBSD12.1-RELEASE-p1 VM. Kinda looks like a maybe simpleNo such file or directory
, however I'm very new to building Rust so I'm not sure. Probably the most relevant output would be:(last lines of output from
x.py dist
):Maybe that's sufficient for you guys to get an idea of the problem?
Much more (maybe unnecessary) details:
I'm trying to cross-compile on a FreeBSD 12.1-RELEASE-p1 (x86_64) VM for aarch64-unknown-freebsd. More precisely, I am trying to, at the same time, get a (x86_64 -> aarch64) and an (aarch64 -> aarch64) rustc, both compiled on x86_64-unknown-freebsd.
My build environment appears to be mostly set up right at this point, as most of the build is working, but I'm having a hard time completing it. I am unsure if the best place to ask is here or on the FreeBSD mailing lists.
It seems the build actually produced the
rustc
andstd
lib. I tested running both the x86_64 and aarch64 producedrustc
withrustc --version
on their respective platforms, and they run.My steps
After setting up the FreeBSD build environment for aarch64 approximately as indicated here (approximately because the doc is a bit dated), the
build
step works fine with this command:My
aarch64.toml
mostly follows the document linked, but that document dates from a few years back, so I had to modify the config a bit to overcome the first build issues.The
dist
step:Produces this output:
Thanks a lot for your time. Any idea?