You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Basically all commercial packages we have that includes some form of GUI has many os dependencies for the entire graphics stack, often also additional requirements that the OS has certain fonts and whatnot installed.
Will they work if we load X11 as a module? Maybe.
Will things break when we load in very new libraries into LD_LIBRARY_PATH? Also likely.
I definitely prefer to not include compiled pieces here, which assuming they would even be ABI compatible, would also mean they are part of toolchains, so I could no longer break out these binary installations (I keep such software trees separate in order not to have to duplicate installations for every CPU architecture in my mixed clusters). Same goes for Mathematica, MATLAB, ABAQUS, COMSOL, and much more (basically all commercial software).
I created a home build of Star-CCM+ 19.02.009-r8 based on 18.04.008-r8 and noticed that certain libraries require X11.
I just added a X11 module in the module file to get around this for now, might be a good idea to consider other ways of resolving this going forward.
The text was updated successfully, but these errors were encountered: