warning: rav1e@0.7.1: Unable to run nasm: No such file or directory (os error 2)

[joepio]

https://github.com/atomicdata-dev/atomic-server/actions/runs/10372329057

Seems like something in the build process fails because rav1e (from the image library) needs an nasm dependency.

[joepio]

 warning: rav1e@0.7.1: This version of NASM is too old: NASM version 2.14

Hmm, looks like apt install nasm installs 2.14 instead of 2.16....

Not sure how I can install it

[joepio]

Welp, looks like Debian only has 2.14 (from 2019)... Maybe I can manually add a newer repo?

[joepio]

Switching to a newer debian image (currently on buster, can go to bookworm) also gave me access to a newer library. Fixed the issue.

[joepio]

Forgot to also add it as a dependency in the docker builds:

https://github.com/atomicdata-dev/atomic-server/actions/runs/10388111184/job/28763030130#step:7:3863

[joepio]

This could be a challenge. Asked for help in the earthly slack.

For my cargo build to succeed, I need to install some linux dependencies.
But I'm not sure where I could do this. The +CROSS command seems to run the whole build step and spin up a linux image where my library isn't installed yet.

# This is not going to work :(
RUN apt install nasm
DO rust+CROSS --target ${TARGET}

Any ideas?

[joepio]

Looks like cross does allow for custom libraries

I should probably create a Cross.toml

[joepio]

I tried adding a Cross.toml:

[target.x86_64-unknown-linux-musl]
pre-build = [
  "dpkg --add-architecture $CROSS_DEB_ARCH",
  "apt-get update",
  "apt-get install --assume-yes nasm:$CROSS_DEB_ARCH",
]

And running:

earthly -i --org ontola --sat henk -P +cross-build --TARGET=x86_64-unknown-linux-musl

But I still get the same issue:

warning: rav1e@0.7.1: Unable to run nasm: No such file or directory (os error 2)

And I can't find the commands anywhere in the logs. I'm assuming they aren't run, because the Cross.toml is somehow ignored. Perhaps I should move it up a dir and import it in the source step:

  COPY --keep-ts Cargo.toml Cargo.lock Cross.toml ./

[joepio]

Ah yes, moving the file up seems to work. However, I dislike having the Cross.toml in the root folder - it should not be applied to atomic-cli or lib.

But if I add WORKDIR server to cross-build , I think the other directories (e.g. ./target) need to be changed.