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
fatal error: caffe/proto/caffe.pb.h: No such file or directory #105
Comments
Were you following the install instructions in the DIGITS README, or the default Caffe instructions? I've never run into that issue before (though a little googling shows that other people have). That step is definitely not necessary for everyone, so I'm not going to add it to the install instructions. Do you have any clues as to why you ran into this problem and I (and most others) didn't? |
Following the DIGITS README. Not sure and when I built (nvidia fork of) caffe on another box, I did not observe. Could there be some race with the parallel build? |
I'm not sure what you mean. Were you building the multi-GPU branch of caffe? That's not going to work with DIGITS (yet). |
No, the normal fork with standard build instructions. I was just spitballing if the make has some issue in when is runs |
Yep, I think you're right. According to @moconnor725, this is a problem with the parallel build path in caffe. Try it without the |
Also solved my problem, thank you! |
I solved it by inputting the commands:
|
@yhlleo I try your method and it works. It is beacause the first time i try to bulid caffe, i dont use 'sudo', and so I get this error. Then I add 'sudo' in front of the command. But I still get the error, beacause the wrong building is still in the caffe folder. So I need to 'make clean' before 'sudo make all'. |
@seashell9 Your answer helped me as well. I didn't include sudo and I got the error. I am not sure why. make all -j8 is also better than make -j8. Thanks. |
When I ran
make all --jobs=4
I got:I solved this by running:
Should those steps be in the Makefile?
The text was updated successfully, but these errors were encountered: