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 <[email protected]> wrote:
> On Wed, 24 Jul 2024 at 19:39, Michael MacIsaac <[email protected]>
> 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 [email protected] 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 [email protected] with the message: INFO LINUX-390 or visit
http://www2.marist.edu/htbin/wlvindex?LINUX-390
