JWasm in Linux exits with nonzero exit code 1 when run with `-h` or `-?` option

[volkertb]

I'm trying to run the JWasm binary inside a Dockerfile after compiling, as a sanity check that the compilation yielded a properly functioning executable. Since jwasm -? and jwasm -h return exit code 1, the build assumes failure.

I can handle that with a (somewhat ugly) workaround, but I don't think the help option should make JWasm exit with a non-zero exit code.

Also, it would be nice if there was a -v or -version option that would list only the first lines with version and copyright information. Basically the opposite of -q or -nologo. Also with a zero exit code.

Thanks!

[lpsantil]

Are you doing RUN jwasm -h just to document the software versions being used?

Easy workaround would be something like RUN jwasm -h || echo

[lpsantil]

I can handle that with a (somewhat ugly) workaround, but I don't think the help option should make JWasm exit with a non-zero exit code.

I agree with this.

[volkertb]

Are you doing RUN jwasm -h just to document the software versions being used?

Easy workaround would be something like RUN jwasm -h || echo

Thanks. I ended up doing the following, since it's a more explicit check:

RUN jwasm -h 2>&1 | grep -q "usage:" && exit 0 || exit 1

And yes, I asked AI to help me with this. I didn't want to spend too much time on it. 😉

But it's still a workaround that I hope we can get rid of soon.

[Baron-von-Riedesel]

Ok, changed: options /? and /h will return with error code 0.

[lpsantil]

RUN jwasm -h 2>&1 | grep -q "usage:" && exit 0 || exit 1

That's just awkward.

If you're also trying to hide the output, try

RUN jwasm -h 2>&1 >/dev/null || echo

2>&1: Redirect stderr to stdout
>/dev/null: Redirect stdout to /dev/null
|| echo: if any of the previous command (jwasm) doesn't return/exit 0, do an echo (which will now return 0) and should also allow the docker build to continue