leptos, cross warning: unable to get metadata for package

[beeb]

Checklist

• I've looked through the issues and pull requests for similar reports

Describe your issue

See https://github.com/beeb/remote-wol-rs/actions/runs/3969612747/jobs/6804578757

I added the vendored version of openssl into my Cargo.toml file, which normally works to build in CI.

For this project however, it complains about /bin/sh: 1: aarch64-linux-gnu-gcc: not found

What target(s) are you cross-compiling for?

aarch64-unknown-linux-gnu

Which operating system is the host (e.g computer cross is on) running?

• macOS
• Windows
• Linux / BSD
• other OS (specify in description)

What architecture is the host?

• x86_64 / AMD64
• arm32
• arm64 (including Mac M1)

What container engine is cross using?

• docker
• podman
• other container engine (specify in description)

cross version

cross v0.2.4 (https://github.com/cross-rs/cross#8c86a98d)

Example

See https://github.com/beeb/remote-wol-rs/actions/runs/3969612747/jobs/6804578757

Additional information / notes

No response

[Emilgardis]

Please note the warning

[cross] warning: unable to get metadata for package
[cross] note: Falling back to `cargo` on the host.

https://github.com/beeb/remote-wol-rs/actions/runs/3969612747/jobs/6804578757#step:6:10

can you reproduce the issue locally?

add -v to see what cargo metadata command is failing

[beeb]

I can't reproduce locally because I'm facing #1189 on my machine and can't even go that far.

Maybe I'm just misunderstanding how I can cross-compile the server part of my leptos application. Normally I would use cargo leptos locally but it doesn't support cross-compile. cargo leptos invokes this command to build the server so I thought that should work:

cargo build --package=remote_wol --bin=remote_wol --target-dir=target/server --no-default-features --features=ssr --release

Let me do a more verbose CI build.

[beeb]

I'll be damned... https://github.com/beeb/remote-wol-rs/actions/runs/3970758818/jobs/6807044897

This time around it went though, with the same command (except for the added -v)

[Emilgardis]

interesting! I guess it was a cosmic ray or something

[beeb]

Can't be reproduced anymore