-
Notifications
You must be signed in to change notification settings - Fork 327
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Linux install script matlab/SWIG bindings connection issues Moco/Tropter #3400
Comments
Your first issue should be solved once #2930 is finished/merged.
Footnotes
|
Hi @cvhammond, I am sorry to hear you are having this issue. This is something we are working on, related to how libraries are loaded in Linux. We are working on fixing this on this PR #2930, as @halleysfifthinc mentioned. If you installed opensim-core or opensim-gui using the install script, you can try the workaround mentioned in opensim-org/opensim-gui#1393. Try executing the following commands before executing opensim or matlab (don't forget to substitute <user_name> with your ubuntu username!):
|
Glad to see this is already on your radar. I tried a few of the suggestions without success; looking forward to the issues being resolved! |
@cvhammond now that PR #2930 is merged, feel free to test the install script again and close the issue if fixed. Thanks for reporting. |
To report: I reinstalled MATLAB, matlab-support (apt-get install) and then OpenSim from the linux-build-script (w/moco) on Ubuntu 22.04. After I found this link showing that you can just copy the Specifically, I can now load the model attached above without error. I have not yet done significant additional testing. Regarding copying the libstdc++, I guess the gcc that ships with MATLAB internally hasn't been updated to later versions and uses an older GLIBCXX but OpenSim expects a newer one or something. Unfortunately, I'm not too booked-up on compiler stuff Technically, using OpenSim with MATLAB out-of-the-box on Ubuntu is not yet possible, please advise to close issue or leave open until the GLIBCXX issue is somehow resolved in the build script. |
Thanks for reporting @cvhammond The bottom line is that the two systems (OpenSim and Matlab) make different choices regarding what low level system libraries are assumed to live on the target machine, and end up relying on different GLIBCXX. The fact that the choices are different is not a bug since we're self-conatined but an issue that clients/users have to contend with. Ideally the advanced cmake dialog would give you option to override the default choices. As such I would test a Moco problem (to exercise other call sequences trough the libraries needed to run Moco) and if all works, then close the issue. We can add a line to documentation somewhere describing the problem and workaround for future users of Matab on linux. Thanks again for your help. |
Attempting to install opensim-core via the install script on Ubuntu 22.04.
If you run the install with Moco then the error:
java.lang.UnsatisfiedLinkError: /home/claire/opensim-core/sdk/lib/libosimJavaJNI.so: libadolc.so.2: cannot open shared object file: No such file or directory
pops up after runningmodel = org.opensim.modeling.Model()
after runningconfigureOpenSim.m
and restarting Matlab.If you look in the directory, there is a file
libadolc.so.2.1.0
which seems similar. I even changed the name of it, but received another linking error.If you download the pre-built Linux build from the
continuous-integration
GitHub Action for this repository with the 'no-moco' tag, then it works out of the box, but crashes on model.initSystem() for the model that we are using without issue elsewhere. I have attached the model, it is a Rajagopal-like model. I assume Moco and associated libraries are required for the model's system to be initialized. An empty model's system can be initialized without crashing.Rajagopal_4.0_RCNL_markers_scaled.zip
Can the install script be updated or is the bug related to how Moco libraries are included and the effect on resultant
libosimJavaJNI.so
file? I've basically reached a dead-end, this is Linux specific because the Matlab bindings are working great for Mac and WindowsThe text was updated successfully, but these errors were encountered: