Support for illumos

[nmartin0]

I would like to use HPC's Open Cluster Scheduler on illumos. I'm running into issues while trying to build it. The docs do appear to suggest that the Open Cluster Scheduler supports Solaris. Would it be possible to add illumos support?

[ernst-bablick]

We build GCS on Solaris 11 without issues. As far as I can remember cmake caused some headache initially. We use cmake-3.27.9 successfully now. Do you have more details in which problems are you running?

I will setup illumos in our Lab when I have some time and let you know about my results.

[nmartin0]

I'm attempting to build OCS/GCS v9.0.3 on OpenIndiana latest. The packages available as of current include cmake v3.31.6, git, gcc 13 and gcc 14, autoconf, and automake. Patchelf isn't available in the package repository; I believe that illumos ships with elfedit instead. Patchelf had to be built. I've attached a log file created from the stderr coming out of the build, which I believe will detail the problems. I did mention this issue to on the illumos outlet and there was a concern about the -std=c99 flag.

I look forward to hearing about your results.

ERRORS.LOG

[ernst-bablick]

Short update: Meanwhile, we have set up VMs with OmniOS and OpenIndiana. I was able to reproduce the build problem and found another problem related to building 3rd_party packages (hwloc). We have a solution and Joachim is currently running our test suite with the created binaries. I expect to see the check-in tomorrow or maybe on Friday.

[nmartin0]

I appreciate the update and info. I'm eager to hear how things go.

[jgabler-hpc]

We added a new architecture osol-amd64 - looks as if there are too many differences between Solaris and Illumos by now, esp. around some shared libraries. Binaries built on Solaris 11 (the sol-amd64 architecture) will not work on Illumos.
The code is checked in, we built and did some testing on Omnios and on OpenIndiana.
The changes were done in the master branch. It should be possible to cherry-pick them to the stable V90_BRANCH, though.
Please give it a try and let us know the result.

[nmartin0]

I attempted to build the clusterscheduler from the master branch on OmniOS today. I noticed the changes made in the 01_prepare_dev_env.md which reflect OpenIndiana, OmniOS, and other distros. I followed this guide and noticed that there is a discrepancy in the packages presented in this list, which I believe reflects the differences in how Omni and OI organize the packages.
Here are my notes regarding where I found the discrepancies where the packages differ on OmniOS;
Legend: unavailable -> available
pkg:/developer/gcc-14 -> pkg:/developer/gcc14
pkg:/developer/debug/gdb -> pkg:/ooce/developer/gdb
pkg:/developer/build/cmake -> pkg:/ooce/developer/cmake
pkg:/terminal/xterm -> (multiple packages returned by doing pkg search xterm)
pkg:/shell/expect -> pkg:/ooce/runtime/expect
pkg:/developer/documentation-tool/doxygen -> (none found via a search)
pkg:/image/graphviz -> pkg:/ooce/application/graphviz
pkg:/image/gnuplot -> pkg:/ooce/application/gnuplot
pkg:/developer/build/maven -> (none found via a search)

I continued to 02_build_configuration.md after installing what was possible. I attempted to run cmake .. [OPTIONS] and received the following CMake error (snippet);
-- We are building the following 3rdparty libraries: CMake Error at CMakeLists.txt:230 (message): JAVA_HOME not set in environment, cannot build JNI code for libdrmaa

I looked through sections 01, 02, and 03 of the development-guide, and did not find a reference to this variable. Is this variable intended to be set by the user?
I believe that the JAVA_HOME variable should be pointed to /usr/jdk/instances/openjdk${version}.

I appreciate the updates to the source to reflect illumos. I'll try the build on OpenIndiana next.
Thank you

[ernst-bablick]

Thanks for your feedback! Feel free to add a new section to the guide that covers OmniOS or change existing sections.

• The package list looks fine. Without xterm you can build but later qsh will not work.
• Yes, JAVA_HOME needs to be set correctly. The path depends on the distribution. On OmniOS I have set it to /usr/java. On OpenIndiana it is set to /usr/jdk/instances/openjdk1.8.0/. Make sure that the directory contains the include subdirectory so the jni.h header file can be found by the build system.
• If you do not intend to build Java DRMAA then you do not need maven.

[nmartin0]

I appreciate the update. I would be glad to modify the sections on the guide. I'll continue testing into next week and can share the results.