Build failing for aarch64-unknown-linx-musl
#578
-
I'm trying to build a simple wry app for My container build script ctr=`buildah from rustembedded/cross:aarch64-unknown-linux-musl-0.2.1`
buildah run $ctr apt-get update
buildah run $ctr apt-get install -y \
libwebkit2gtk-4.0-dev \
libgtksourceviewmm-3.0-dev \
libc6-dev-i386 \
clang
buildah commit $ctr cross-wry:aarch64-unknown-linux-musl-0.2. My [target.aarch64-unknown-linux-musl]
image="cross-wry:aarch64-unknown-linux-musl-0.2.1" This results in
I'm very new to linking so I'm not really sure where to start debugging. My best guess here is that packages installed to the container aren't appropriate for this build, perhaps because of architecture. This is related to this issue. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
Sorry for the late response. There's a few issues here: one is that you're using packages linked against |
Beta Was this translation helpful? Give feedback.
Sorry for the late response. There's a few issues here: one is that you're using packages linked against
glibc
for amusl
build. This may work fine during compilation, but the binary is unlikely to run. Next, you're using much older versions of our images: v0.2.1. Try usingghcr.io/cross-rs/aarch64-unknown-linux-musl:0.2.4
(latest release) orghcr.io/cross-rs/aarch64-unknown-linux-musl:main
(latest development branch, which uses a newer Ubuntu base). However, it will likely be a better idea to use an Alpine-based image for this purpose. I've been meaning to add anx86_64-unknown-linux-musl
Alpine image just like how we support a CentOS one forx86_64-unknown-linux-gnu
. You will likely hav…