Support s390x

[v1gnesh]

Hello,

Can you please guide me on what's required to get nx working in s390x, and to subsequently include the building of artifacts for this platform. @pleia2 can help arrange a GHA runner in s390x, to make it a part of your regular CI.

Background: Trying to build Grafana 11 for linux/s390x - grafana/grafana#24273 (comment)

[FrozenPandaz]

If I understand this correctly, you want to build a binary of Grafana which can run on s390x.
So you want to run build through Nx on a s390x machine to build the binary of Grafana?

We are working towards compiling a wasm build of the Nx binary which can be used by any system including s390x that we don't explicitly build for. #22870

We expect to have it done soon.

[v1gnesh]

So you want to run build through Nx on a s390x machine to build the binary of Grafana?

Yup. Grafana 11 seems to be using nx now.

I haven't dug into the CI setup of nx yet. Any pointers you can share on how I can produce something like this -
https://www.npmjs.com/package/@nx/nx-linux-x64-gnu

That is, @nx/nx-linux-s390x-gnu ... will really help 🙏

[nealef]

I am interested in this support and would like to contribute. However, it appears that to be able to build nx you need to use nx. I have a patch-set that could be used as a starting point and builds cleanly on x64 but there are some rust compiles in there implying there is platform-specific code. This would seem to mean a cross-build would be required - unless it's just used during the build process.

I am able to set up a git actions runner for s390x if that would help.

Going through the build steps in your instructions I end up with a local registry containing:

README.md node_modules nx.json package-lock.json package.json packages

In node_modules/nx/bin:

init-local.d.ts init-local.js nx-cloud.d.ts nx-cloud.js nx.d.ts nx.js post-install.d.ts post-install.js run-executor.d.ts run-executor.js

I have created a draft PR just so I can make my changes visible: #26772

Neale

[nealef]

There's a bin/post-install.ts file so I assume I should be running tsc against it to create bin/post-install.js but I am not sure of the correct incantation nor why it's not automatically done as part of the pnpm i process.

[v1gnesh]

This untangling process is really challenging; multiple knots to "reverse engineer" - their CI process to see what the commands are, what the env is, how to use WASM, its pre-req, etc.

A lot of this work will become obsolete if only IBM could put some force into getting s390x CI runners supported & made available via GitHub itself... @jmertic @pleia2.
I understand you (Neil) play a pivotal part in the technology enablement of this too :)

Could you clarify please, so you've tried to a) cross-compile for s390x, from x64 b) make the wasm branch work.
Have you tried with rustc directly in linux/s390x? I find these front-end projects pretty overwhelming..

[chegde20121]

@v1gnesh I also came across same issue. I am trying to port an internal repo which uses nx on s390x. I got the below error
9772 verbose Linux 5.14.0-427.20.1.el9_4.s390x 9773 verbose node v16.20.2 9774 verbose npm v8.19.4 9775 error code EBADPLATFORM 9776 error notsup Unsupported platform for @nrwl/nx-linux-x64-gnu@15.8.7: wanted {"os":"linux","arch":"x64"} (current: {"os":"linux","arch":"s390x"})

is there any solution you are aware of?

[v1gnesh]

Not yet. nx the project wants us to add support for linux/s390x by building via their wasm route.

[jmertic]

Hi all! While we don't have the resource available right now, we should later this year have an s390x Linux VM that this project can use. More details and the request process is outlined at https://tac.openmainframeproject.org/programs/infrastructure