-
-
Notifications
You must be signed in to change notification settings - Fork 3
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
More user-friendly procedure to avoid crash due to wrong libstdc++.so
#53
Comments
|
|
I also tried it out with an older MATLAB version on my system. This makes things even more confusing... |
Also no problems with MATLAB R2023b on my system. This is confusing for me considering what @NiklasVin reports above. Currently it looks like I cannot reproduce the problem. |
With R2020b I can reproduce the problem and get the following error:
|
|
I tried to find a bugfix or similar hinting in this direction in the changelogs of MATLAB, but could not find anything. Therefore, I asked a question in the MATLAB Community forum: https://de.mathworks.com/matlabcentral/answers/2108031-has-issue-with-libstdc-so-6-been-fixed. |
Refer to #53 and provide more information.
|
Were the MATLAB versions for which the resonant circuit example worked for you fresh installations? |
In our
README.md
we suggest the following procedure to start MATLAB, if versionGLIBCXX_#.#.##
is not found:This follows the suggested approach from here.
I'm a bit unsure whether we should generally follow this procedure (assuming it is always or in most cases required) or rather treat it as pure troubleshooting (exceptional cases). I was a bit surprised that I actually do not need to set
LD_PRELOAD
on my system. Running the example case from precice/tutorials#480 worked for me without the need to setLD_PRELOAD
.There is also a list of supported gcc versions and this looks like we don't need to worry a lot. I would still suggest to keep the remark in the troubleshooting section, because I'm not a big fan of the fact that MATLAB brings along its own
libstdc++.so
and I assume this might lead to compatibility problems sooner or later.I think it would be helpful to collect some data here in the comments and then decide what we should tell our users (and how to design the tutorials).
suggested format
gcc --version
): ...matlab -nodisplay -r "disp(version);exit;"
): ...LD_PRELOAD
: yes/noImportant: We should also check this for the VM.
The text was updated successfully, but these errors were encountered: