lrose-core builds fail on alma9

[isabels]

Hi all,

I'm trying to build the master branch of lrose-core on an ISS field server running Alma 9 (9.4/Seafoam Ocelot). Both the build_lrose_manual and build_lrose_cmake scripts to build lrose fail before building RadxConvert or Hawkeye, the tools I need for ISS lidar processing.

I ran the install_linux_packages script on the data manager, which completed successfully, so the build environment should be set up correctly.

I've attached the output from running these commands, each from a clean checkout of the master branch:

• [iss@iss2 lrose-core]$ build/scripts/build_lrose_manual.py --debug --verbose --prefix /opt/iss-system/lrose > build_manual.txt 2>&1
• [iss@iss2 lrose-core]$ build/scripts/build_lrose_cmake.py --debug --verbose --prefix /opt/iss-system/lrose > build_cmake.txt 2>&1

Both fail pretty early in the build process. I don't know enough about the lrose build system to figure out what the problem is, but hopefully the output is helpful.

Have you successfully built lrose on other alma9 systems? Is this just something unexpected about the environment on ISS servers, or am I going about this the wrong way?

As a side note, this data manager originally had the fix-alma9-packages branch checked out, which was last updated May of 2023. At that point, lrose built successfully on alma9 using both manual and cmake build scripts. Moving forward to the current master branch (to get some fixes for leosphere format data that I made last summer) is when builds stopped working...

Thanks!
Isabel
build_cmake.txt
build_manual.txt

[burghart]

Hi Isabel, I know the docs and scripts are behind the times, but here's a quick recipe that works with the *current* lrose-core master branch on an AlmaLinux 9 machine: $ cd ~/git $ git clone https://github.com/NCAR/lrose-core $ cd lrose-core $ build/scripts/createCMakeLists.py # add "--prefix <dir>" to install somewhere other than ~/lrose $ cmake -S . -B build # this will add a bunch of CMake stuff to the repo's existing "build" directory :-( $ cd build $ make $ make install # or "sudo make install" if needed for the desired install location Chris

…

On Tue, Oct 15, 2024 at 1:59 PM Isabel Suhr ***@***.***> wrote: Hi all, I'm trying to build the master branch of lrose-core on an ISS field server running Alma 9 (9.4/Seafoam Ocelot). Both the build_lrose_manual and build_lrose_cmake scripts to build lrose fail before building RadxConvert or Hawkeye, the tools I need for ISS lidar processing. I ran the install_linux_packages script on the data manager, which completed successfully, so the build environment should be set up correctly. I've attached the output from running these commands, each from a clean checkout of the master branch: - ***@***.*** lrose-core]$ build/scripts/build_lrose_manual.py --debug --verbose --prefix /opt/iss-system/lrose > build_manual.txt 2>&1 - ***@***.*** lrose-core]$ build/scripts/build_lrose_cmake.py --debug --verbose --prefix /opt/iss-system/lrose > build_cmake.txt 2>&1 Both fail pretty early in the build process. I don't know enough about the lrose build system to figure out what the problem is, but hopefully the output is helpful. Have you successfully built lrose on other alma9 systems? Is this just something unexpected about the environment on ISS servers, or am I going about this the wrong way? As a side note, this data manager originally had the fix-alma9-packages branch checked out, which was last updated May of 2023. At that point, lrose built successfully on alma9 using both manual and cmake build scripts. Moving forward to the current master branch (to get some fixes for leosphere format data that I made last summer) is when builds stopped working... Thanks! Isabel build_cmake.txt <https://github.com/user-attachments/files/17384304/build_cmake.txt> build_manual.txt <https://github.com/user-attachments/files/17384305/build_manual.txt> — Reply to this email directly, view it on GitHub <#133>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA42O2KTKGFFBR7VEQUAUB3Z3VX3BAVCNFSM6AAAAABP7474RGVHI2DSMVQWIX3LMV43ASLTON2WKOZSGU4DSNZVGIZTQMA> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>