More user-friendly procedure to avoid crash due to wrong libstdc++.so #53
Description
In our README.md we suggest the following procedure to start MATLAB, if version GLIBCXX_#.#.## is not found:
LD_PRELOAD=/usr/lib/x86_64-linux-gnu/libstdc++.so.6 matlab
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 set LD_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 (
gcc --version): ... - MATLAB version (
matlab -nodisplay -r "disp(version);exit;"): ... - tutorial/solverdummy works without setting
LD_PRELOAD: yes/no
Important: We should also check this for the VM.