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
"Invalid MEX-file" and "Missing dependent shared libraries", Matlab 2017a, MacOS 10.12 #151
Comments
I met the same problem. Actually, I reinstalled the MATLAB and get the above results when I run vlfeat. However, I don't know how to solve it. |
I also had the same problem. This can be solved by recompiling the library following the instruction described in http://www.vlfeat.org/compiling-unix.html. I used: Hope this helps |
Thanks, it works. |
Hi, I face the same problem. I type "make MEX=/Applications/MATLAB_R2017a.app/bin/mex ARCH=maci64" in terminal but it shows "make: *** No targets specified and no makefile found. Stop." Did I miss any steps? |
Did you change your working directory to VLFEATROOT according to http://www.vlfeat.org/compiling-unix.html? There should be a makefile in that directory. It worked for me. |
Thanks for your quick reply. Yeah, I tried but there is still something wrong. I downgraded my MATLAB to 2016b finally. It became normal. |
It worked for me. Did you make sure to compile Matlab support? |
I face the same problem. It's really hard to use MATLAB 2017a in iOS 10.12.5.
|
@zzzyq same as you. it does not work. I am not sure what happened. |
Sorry to revive an old thread but I am stuck on this. I am using Mac OS 10.13.6 and Matlab 2015a. I followed instructions on this website:
I get
So I tried to follow instructions here about clang: But when I try
I get
Any advice much appreciated! |
I got the error below after I upgrade Matlab from 2016b to 2017a:
Invalid MEX-file
Plus a bunch of missing symbols like:
I did not make any change on vlfeat folder, and 'libvl.dylib' is right under the '/toolbox/mex/mexmaci64/' folder.
Is someone able to run vlfeat with Matlab 2017a on MacOS?
The text was updated successfully, but these errors were encountered: