search

rcenvironment / rce

Distributed, workflow-driven integration environment
https://rcenvironment.de/
51 stars 16 forks source link

Updating dependencies from libgfortran3 to libgfortran5 #43

Closed tfoerst3r closed 2 years ago

tfoerst3r commented 2 years ago

During my installation process, I came across the following error:

error: Failed dependencies:
        libgfortran.so.3()(64bit) is needed by rce-10.3.0.202112090919-standard.x86_64

It seems that most modern Linux desktop systems do not support libgfortran3 anymore. Please consider updating the dependency.

rmischke-dlr commented 2 years ago

Hi, thanks for the feedback.

We are aware of this problematic dependency, but it is difficult to remove in the short term. The dependency is, however, not needed by RCE itself, but only be the Dakota optimizer binary that we ship as part of the package. If you do not plan to use the optimizer, you can install the RCE package with flags to override/ignore this dependency (e.g. rpm --nodeps), and everything should work normally.

In the next major release cycle, RCE 11.x, we will no longer include the Dakota binary in the RCE package, so the dependency will no longer be an issue. In RCE 10.x, however, we have to keep the binary as part of our backwards compatibility policy.

Upgrading the dependency to libgfortran5 would probably break the current Dakota binary, and patching and rebuilding Dakota has proven to be quite tricky. We also already tried to statically compile that dependency into the Dakota binary, but with no success so far.

tfoerst3r commented 2 years ago

rpm --nodeps worked but a new error occurred. 

Caused by: de.rcenvironment.core.configuration.bootstrap.profile.ProfileException: 
Unexpected error when trying to acquire a file lock on /home/<home>/.rce/default/instance.lock`

Currently the domain https://software.dlr.de/ is not reachable. So no documentation can be downloaded. I am not sure how to install rce on openSUSE at this point. Thx for the hint and any help would be appreciated.

rmischke-dlr commented 2 years ago

That ProfileException error is odd -- in the "normal" case that the profile directory was simply locked (because another instance was already using it), this should be caught and replaced with a more user-friendly message. Could you post the section from /home/<home>/.rce/default/debug.log that surrounds that error, or send us the whole zipped debug.log via email (the address on the website's starting page, above the news section)?

I suppose that you just started RCE without any special parameters? Did you launch it via GUI or from the command line?

The domain being down happened at the end of last week after a server reboot, and was fixed Monday morning. Sorry for the inconvenience.

rmischke-dlr commented 2 years ago

Please reopen this issue if you need additional feedback.

Regarding the main issue, as mentioned above, the fix will have to wait for RCE 11.0.0 for compatibility reasons.