Re: [petsc-dev] Matlab interface issue

Barry, yes, it does what is needed. However, I found one more small problem: make check was throwing dyld: Library not loaded: @rpath/libicudata.56.dylib Referenced from: /Users/vhapla/petsc1/src/snes/examples/tutorials/ex19 Reason: image not found I fixed it locally just by adding

Re: [petsc-dev] Matlab interface issue

Please try the branch barry/feature-matlab-socket/maint and --with-matlab-socket=0 and let me know if it works. Barry > On Apr 17, 2018, at 3:16 AM, Vaclav Hapla wrote: > > OK. But definitely it's tricky that you try to inject all PETSc compiler > options

Re: [petsc-dev] Matlab interface issue

OK. But definitely it's tricky that you try to inject all PETSc compiler options to the mex wrapper which is by documentation only tested with Xcode and Intel and it's always set up just for one compiler (see mex -setup). Hence, I would at least vote for config option to turn off this socket

Re: [petsc-dev] Matlab interface issue

Hmm, I tried on my Mac and had the same problem. But then I upgraded from Matlab 2017A to 2018A and boom the problem went away and it was able to build the socket mex files without a problem. So my conclusion is that we shouldn't change anything in the PETSc makefiles? Barry > On Apr 16,

[petsc-dev] Matlab interface issue

Hello I need to compile PETSc with MATLAB interface on Mac OS. First thing is that Mex supports only Xcode or Intel compilers, not GCC. So I compiled PETSc with Xcode, using options --with-cc="/usr/bin/xcrun -sdk macosx10.13 clang" --with-matlab --with-matlab-arch=maci64 --with-matlab-engine