musl / alpine linux support

[lholden]

Environment information

Unfortunately, I can't run the `rome rage` command due to the issue in question.

Using docker image `node:16-alpine`, which uses alpine / musl.

What happened?

Tried to run rome on our CI pipeline, only to discover the binary isn't able to run in the node:16-alpine image we are using for this.

Most likely due to it using musl instead of glibc.

Expected result

rome to work on my CI pipeline ;)

Specifically, I think it would make sense if musl targets got added as a release artifacts, and for those to be pulled down instead of linux-x86.

Code of Conduct

• I agree to follow Rome's Code of Conduct

[sebmck]

Likely the same issue as #3549.

[lholden]

Seems like the other issue was related to the binary depending on a newer version of glibc than what was shipped in CentOS, where this is specifically a problem where musl (glibc replacement) is used.

So... might be the same issue, or at least, having the same solution? For example, statically linking to all glibc libs might solve both issues.

I wasn't really sure if it would make sense to contribute to that issue or create a new one :)

[MichaReiser]

The two are related but require slightly different solutions

Supporting musl requires a separate Rome build for every platform that links against musl instead of glibc. Musl is a Tier 2 target of Rusttier 2

[Conaclos]

With gcompat I encountered an error with pico-args that I reported. It could be nice to see if we got new problems once #4405 merged.

[pacak]

It could be nice to see if we got new problems once #4405 merged.

I'm curious as well. I've confirmed that basic examples x86_64-unknown-linux-musl works as expected, maybe gcompat is doing something fishy when there's no arguments.

@Conaclos how do I run anything with alpine/gcompat?

[Conaclos]

@pacak You just need to install gcompat:

apk add gcompat

[pacak]

I'm on Ubuntu so it won't work :) Any ready made docker script that I can hack or anything like that?

[Conaclos]

Ah sorry I tested on q fresh installation. I did not test with a container...

[pacak]

Well, FWIW cargo-show-asm I downloaded with cargo-binstall works in docker with alpine linux and gcompat installed but I imagine it was compiled for musl specific target. cargo-show-asm should be using bpaf 0.8. A few examples I compiled myself with --target x86_64-unknown-linux-musl worked fine as well. I couldn't get native glibc examples compiled on my machine to run - fails with strange linker errors.

rome I downloaded from the releases pages failed to run without libgcc and once I installed that it failed to get any command line arguments from std::env::args_os(). So something breaks std::env::args_os() and std::env::args() that uses it.

A simple replication - this should print something like ArgsOs { inner: ["target/debug/foo"] }.

fn main() {
    println!("{:?}", std::env::args_os());
}

There's not much I can do to support it, but compiling for musl target specifically should work.