Combination of MATLAB release and OS forces restriciton on C++ compiler about matlab-sqlite3-driver HOT 3 OPEN

@ruimaciel Thanks for reporting the issue. I don't have that specific environment, but depending on the compiler config, it might be possible to workaround the restriction. The usual approach to debug this is to add -v flag in MEXFLAGS in Makefile and see the error message.

from matlab-sqlite3-driver.

I've spent some time looking into this issue and I believe I've jumped the gun on this issue.

The good news is that it's possible to get matlab-sqlite3-driver to run on Matlab 2051a on Debian 8 without any compiler checks, in spite of Matlab only supporting gcc v4.7. The somewhat bad news is that it takes a bit of tinkering to circumvent some compiler issues and get things to run.

From what I've gathered, Matlab 2051a comes bundled with libstdc++.so.6.0.17, which appears to be the libstdc++ associated with g++4.7, the only version of GCC supported by Matlab. If g++4.7 isn't installed and the end-user tries to use a different version of GCC to handle their MEX business, Matlab will throw an error.

To circumvent this error, all it takes is to link Matlab's copy of libstdc++.so.6 (which is a symbolic link to Matlab's copy of libstdc++.so.6.0.17, which comes bundled with Matlab) to the operating system's copy of libstdc++.so.6, which comes bundled with G++.

In Debian8, G++ 4.9 comes bundled with libstdc++.so.6.0.20. I've added a symbolic link to this library in ${MATLAB R2015a}/sys/os/glnxa64, and then proceeded to replace Matlab's symlink to libstdc++.so.6.0.17 with a symlink to the libstdc++.so.6.0.20 link I've added to the folder.

After restarting Matlab, matlab-sqlite3-driver ran as expected.

from matlab-sqlite3-driver.

@ruimaciel Alright, that's a runtime issue, not a compilation issue. The easiest (and least destructive) workaround is actually to launch Matlab with LD_PRELOAD flag. e.g.,

LD_PRELOAD=/usr/lib/x86_64-linux-gnu/libstdc++.so.6 matlab

from matlab-sqlite3-driver.