Glibc errors with v0.2.2

[ravenclaw900]

Checklist

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

Describe your issue

Cross returns glibc build script errors on aarch64-unknown-linux-musl and arm-unknown-linux-musleabihf with the new version.

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

aarch64-unknown-linux-musl, arm-unknown-linux-musleabihf

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

v0.2.2

Example

Armv6: https://github.com/ravenclaw900/DietPi-Dashboard/runs/7050663794
Aarch64: https://github.com/ravenclaw900/DietPi-Dashboard/runs/7050775525
Rebuild of previously working code: https://github.com/ravenclaw900/DietPi-Dashboard/runs/7051046368

Additional information / notes

From #724, running cargo clean or building without the cache didn’t help.

[Alexhuszagh]

Can you give me detailed instructions on how to build your library? I've tried just the simple in the backend directory but I'm assuming I need to do something else. Edit: Nevermind, the Makefile was simple and clear.

cross build --release --target arm-unknown-linux-musleabihf --features compression

But if this does reproduce faithfully, this might be the best way we can diagnose and fix #724, so thank you.

[Alexhuszagh]

This will take me a while to debug, and I'll be off tomorrow so it'll likely be Sunday or early next week, but it's not reproducing every time for arm-unknown-linux-musleabihf on my end.

I've run the following sequence:

git clone https://github.com/ravenclaw900/DietPi-Dashboard --depth 1
cd DietPi-Dashboard
cd src/frontend
yarn build
cd ../..
cp -r src/frontend/dist src/backend
cross build --release --target arm-unknown-linux-musleabihf --features compression

I'll try extensively debugging this, and sometimes issues arise when mixing toolchains so I'll try that too.

[Emilgardis]

Related to #724, this one doesn't seem to be solved with a clean however

[Emilgardis]

The issue, I think, is that somehow, we're using /target/release/build/dep-deadbeef/build-script-build instead of /target/<target>/release/build/dep-deadbeef/build-script-build

[Emilgardis]

Removing all build-script-builds in target/release/deps and target/release/build is enough.

I believe this is related rust-lang/cargo#10367 (comment)

[ravenclaw900]

That didn't seem to work: https://github.com/ravenclaw900/DietPi-Dashboard/runs/7054638003.

[Emilgardis]

Sorry, I meant remove all dependencies of the buildscript, so remove every folder with a build-script. I just removed the full folders.

This is essentially a cargo clean but worse.

[ravenclaw900]

Alright, deleting all the build folders and all the .so files let it compile. Luckily, this should only be required when compiling dependencies with build scripts, so it can be removed most of the time.

[rafaelmaeuer]

I had this error when building binaries for different platforms with a bash-script. Deleting target/release after every build solved it for me.

[Alexhuszagh]

Closing as a duplicate of #724.