Yeah, it looks like many developers bring their own favorite build tools. I was triggered by Mike's reference to yarn because I started two years ago to tweak stuff in yarn and Grafana to make it build on s390x. I think yarn had dropped the ability to dynamically build big-endian binaries when needed, but once we had the version that could, it turned out that the experimental SWC couldn't be done for s390x even when yarn asked nicely. With Grafana 10.4 my script to rip out SWC didn't work anymore, so I gave up building the front-end application on s390x. As the front-end code is the same for both platforms, I decided to take the front-end from the x64 package and include that in the s390x build. It's a lot quicker and I don't have the ongoing issue with missing dependencies for the build process. When I was doing RPM packages, I probably would have wanted that in a noarch package.
We envisioned that some z/VM Performance Data Pump users might want a supported Grafana on s390x, but my contacts at Grafana were not very interested in the idea. The Grafana Cloud route might be an option for those clients. Rob On Thu, 25 Jul 2024 at 04:49, kekronbekron <kekronbek...@protonmail.com> wrote: > Hey Lyz, > > As Rob mentions, this has become quite a web of dependencies. > Neale sent an s390x PR (https://github.com/nrwl/nx/pull/26772) for nx (a > build tool), but the repo owner said to build through WebAssembly instead > (wasm/wasi support merged recently - https://github.com/nrwl/nx/pull/22870). > And that they won't add any other architectures to their builds. > > nx depends on @napi-rs/cli, which, recently added support for s390x, but > then don't publish binaries for it. > https://github.com/napi-rs/napi-rs/pull/1901 > https://github.com/napi-rs/napi-rs/pull/2028 > https://github.com/napi-rs/napi-rs/releases/tag/napi%403.0.0-alpha.1 > > You'll know from your experience working with OSS projects already Lyz, > that adding s390x support can become quite a journey for each OSS project. > Does GitHub the org look like they'll add this platform as a runner > option, if some instances (in IBM community cloud) are made available to > them via APIs? > I see self-hosted is now possible. As a next step maybe, if GH can show > the ability to get linux/s390x in their interface, but then route the > (free) registration via your org... > > In this case however, even if Microsoft/GitHub provided s390x CI runners > natively via GitHub, I'm not sure if the proj will have used it. > > > -KB > > > On Thursday, July 25th, 2024 at 05:14, Michael MacIsaac < > mike99...@gmail.com> wrote: > > > Rob, > > > > In retrospect, yarn appears to have been installed by build_grafana.sh in > > /usr/local/bin. Even though that was in the PATH by the calling shell, it > > appeared not to be during execution. Making the symbolic link from /bin/ > > resolved that issue. We are still digging on why the build failed much > > later on make build-js. > > > > -Mike Mac > > > > > > On Wed, Jul 24, 2024 at 5:24 PM Rob van der Heij rvdh...@gmail.com > wrote: > > > > > On Wed, 24 Jul 2024 at 19:39, Michael MacIsaac mike99...@gmail.com > > > wrote: > > > > > > > Elizabeth, > > > > > > > > Thanks for the quick response. > > > > > > > > More observations: > > > > - build_go.sh also does not support RHEL 9.4 > > > > - Fixed it, then failed with build_grafana.sh: line 126: yarn: > command > > > > not > > > > found > > > > > > I believe the yarn part is because they dropped big-endian support > > > somewhere along the lines. I had to get an early yarn-4.0.0 to get that > > > resolved. Several things get into that build process that have no s390x > > > version. The latest one was "nx" as far as I recall, and you might > have to > > > talk to Sir Neale who apparently contributed the update for them. > > > I have decided to change the build process and only build the back-end > on > > > s390x, and get the pre-built front-end parts from x64. If you know > where to > > > look, you might find the s390x Docker images. > > > > > > Rob > > > > > > ---------------------------------------------------------------------- > > > For LINUX-390 subscribe / signoff / archive access instructions, > > > send email to lists...@vm.marist.edu with the message: INFO LINUX-390 > or > > > visit > > > http://www2.marist.edu/htbin/wlvindex?LINUX-390 > > > > > > > > -- > > -Mike MacIsaac > > > > ---------------------------------------------------------------------- > > For LINUX-390 subscribe / signoff / archive access instructions, > > send email to lists...@vm.marist.edu with the message: INFO LINUX-390 > or visit > > http://www2.marist.edu/htbin/wlvindex?LINUX-390 > > ---------------------------------------------------------------------- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or > visit > http://www2.marist.edu/htbin/wlvindex?LINUX-390 > ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www2.marist.edu/htbin/wlvindex?LINUX-390
