-
Notifications
You must be signed in to change notification settings - Fork 18.7k
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
Problem building matcaffe with XCode 6 #1212
Comments
Yes, same error here for make matcaffe with OS X 10.9.5 |
Perhaps the vecLib path has changed in the latest Xcode. Try to patch the On Thu, Oct 2, 2014 at 5:31 PM, damro notifications@github.com wrote:
|
That should have been try to patch your mexopts.sh build configuration, not On Thu, Oct 2, 2014 at 5:47 PM, Evan Shelhamer <
|
You can get over the vecLib hump with the following change:
(saw this on caffe users google groups IIRC). After this, I encountered a LD-related error that I resolved by pointing to the correct C++ run-time. (libstdc++) This allowed me to build the mex binary but I haven't tested it out to ensure it works correctly at run-time. |
Here's a Makefile patch against 5c4125d (master): https://gist.github.com/drdan14/19596fe46d4b92db2012 This solves the However, after applying that patch, I run into other errors that look like this:
|
Fix available in #1310 |
Credit @vimalthilak for coming up with it |
This should be fixed with #1740. Please follow-up if not. Sorry for the turnaround time on 10.10! |
Hi, I add this in my Makefile according to vimalthilak' suggestion, but it still comes the error "ld: framework not found vecLib". Could you help me of that? |
I have the same error as well |
Using the dev branch, commit 6af4575, I get the following error when running
make matcaffe
:I have what I believe is the latest version of XCode 6 (Version 6.0.1 (6A317)) and command line tools (6.0.0.0.1.1410400753) installed:
Here's my
Makefile.config
: https://gist.github.com/drdan14/cedd7c5eab6ba503c16bI'm on a Macbook Air with no GPU and OS X 10.9.5.
The text was updated successfully, but these errors were encountered: