Hi, I just change to Sierra and when trying to install CVX I get the following errors when the “Simple Test” is run.
Missing symbol ‘_wmemcmp’ required by
’/usr/lib/libstdc++.6.dylib->/Users/fruzti/cvx/sedumi/partitA.mexmaci64’
Missing symbol ‘_wmemcpy’ required by
’/usr/lib/libstdc++.6.dylib->/Users/fruzti/cvx/sedumi/partitA.mexmaci64’
Missing symbol ‘_wmemmove’ required by
’/usr/lib/libstdc++.6.dylib->/Users/fruzti/cvx/sedumi/partitA.mexmaci64’
Missing symbol ‘_wmemset’ required by
’/usr/lib/libstdc++.6.dylib->/Users/fruzti/cvx/sedumi/partitA.mexmaci64’
Missing symbol ‘_write’ required by
’/usr/lib/libstdc++.6.dylib->/Users/fruzti/cvx/sedumi/partitA.mexmaci64’
Missing symbol ‘_writev’ required by
’/usr/lib/libstdc++.6.dylib->/Users/fruzti/cvx/sedumi/partitA.mexmaci64’.
What version of MATLAB are you using? We’re not able to support R2017a yet. I use CVX on Sierra without incident but only with earlier versions of MATLAB.
Thanks for the answer mcg, indeed is R2017a (now it is clear to me why), however at night I got working CVX 3.0 Build 1177 by a couple of changes in mexopt.sh and by re-building with the optimisation of the object code for SDPT3. It seems to work somehow but I’ll be running some testing to check if something weird pops up.
When I try to build and use the sedumi mex files, cvx_setup throws an error saying that they are old versions that could produce unexpected results and are required to be removed (at the end cvx requests to remove everything), I’ll see if I can come up with momentary solution for this.
Thank you! I’ve been able to run R2017a with CVX by recompilation. The problem is that I really can’t support CVX if I require others to do the recompilation, and I don’t yet have a system that allows me to ship multiple MEX file versions for the same platform. So I’m still figuring out the right way to proceed here.