--- /dev/null
+---
+title: Installation: OS X
+---
+
+# OS X Installation
+
+We highly recommend using the [Homebrew](http://brew.sh/) package manager.
+Ideally you could start from a clean `/usr/local` to avoid conflicts.
+In the following, we assume that you're using Anaconda Python and Homebrew.
+
+**CUDA**: Install via the NVIDIA package that includes both CUDA and the bundled driver. **CUDA 7 is strongly suggested.** Older CUDA require `libstdc++` while clang++ is the default compiler and `libc++` the default standard library on OS X 10.9+. This disagreement makes it necessary to change the compilation settings for each of the dependencies. This is prone to error.
+
+**Library Path**: We find that everything compiles successfully if `$LD_LIBRARY_PATH` is not set at all, and `$DYLD_FALLBACK_LIBRARY_PATH` is set to to provide CUDA, Python, and other relevant libraries (e.g. `/usr/local/cuda/lib:$HOME/anaconda/lib:/usr/local/lib:/usr/lib`).
+In other `ENV` settings, things may not work as expected.
+
+**General dependencies**
+
+ brew install --fresh -vd snappy leveldb gflags glog szip lmdb
+ # need the homebrew science source for OpenCV and hdf5
+ brew tap homebrew/science
+ hdf5 opencv
+
+If using Anaconda Python, a modification to the OpenCV formula might be needed
+Do `brew edit opencv` and change the lines that look like the two lines below to exactly the two lines below.
+
+ -DPYTHON_LIBRARY=#{py_prefix}/lib/libpython2.7.dylib
+ -DPYTHON_INCLUDE_DIR=#{py_prefix}/include/python2.7
+
+If using Anaconda Python, HDF5 is bundled and the `hdf5` formula can be skipped.
+
+**Remaining dependencies, with / without Python**
+
+ # with Python pycaffe needs dependencies built from source
+ brew install --build-from-source --with-python --fresh -vd protobuf
+ brew install --build-from-source --fresh -vd boost
+ # without Python the usual installation suffices
+ brew install protobuf boost
+
+**BLAS**: already installed as the [Accelerate / vecLib Framework](https://developer.apple.com/library/mac/documentation/Darwin/Reference/ManPages/man7/Accelerate.7.html). OpenBLAS and MKL are alternatives for faster CPU computation.
+
+**Python** (optional): Anaconda is the preferred Python.
+If you decide against it, please use Homebrew.
+Check that Caffe and dependencies are linking against the same, desired Python.
+
+Continue with [compilation](installation.html#compilation).
+
+## libstdc++ installation
+
+This route is not for the faint of heart.
+For OS X 10.10 and 10.9 you should install CUDA 7 and follow the instructions above.
+If that is not an option, take a deep breath and carry on.
+
+In OS X 10.9+, clang++ is the default C++ compiler and uses `libc++` as the standard library.
+However, NVIDIA CUDA (even version 6.0) currently links only with `libstdc++`.
+This makes it necessary to change the compilation settings for each of the dependencies.
+
+We do this by modifying the Homebrew formulae before installing any packages.
+Make sure that Homebrew doesn't install any software dependencies in the background; all packages must be linked to `libstdc++`.
+
+The prerequisite Homebrew formulae are
+
+ boost snappy leveldb protobuf gflags glog szip lmdb homebrew/science/opencv
+
+For each of these formulas, `brew edit FORMULA`, and add the ENV definitions as shown:
+
+ def install
+ # ADD THE FOLLOWING:
+ ENV.append "CXXFLAGS", "-stdlib=libstdc++"
+ ENV.append "CFLAGS", "-stdlib=libstdc++"
+ ENV.append "LDFLAGS", "-stdlib=libstdc++ -lstdc++"
+ # The following is necessary because libtool likes to strip LDFLAGS:
+ ENV["CXX"] = "/usr/bin/clang++ -stdlib=libstdc++"
+ ...
+
+To edit the formulae in turn, run
+
+ for x in snappy leveldb protobuf gflags glog szip boost boost-python lmdb homebrew/science/opencv; do brew edit $x; done
+
+After this, run
+
+ for x in snappy leveldb gflags glog szip lmdb homebrew/science/opencv; do brew uninstall $x; brew install --build-from-source --fresh -vd $x; done
+ brew uninstall protobuf; brew install --build-from-source --with-python --fresh -vd protobuf
+ brew install --build-from-source --fresh -vd boost boost-python
+
+If this is not done exactly right then linking errors will trouble you.
+
+**Homebrew versioning** that Homebrew maintains itself as a separate git repository and making the above `brew edit FORMULA` changes will change files in your local copy of homebrew's master branch. By default, this will prevent you from updating Homebrew using `brew update`, as you will get an error message like the following:
+
+ $ brew update
+ error: Your local changes to the following files would be overwritten by merge:
+ Library/Formula/lmdb.rb
+ Please, commit your changes or stash them before you can merge.
+ Aborting
+ Error: Failure while executing: git pull -q origin refs/heads/master:refs/remotes/origin/master
+
+One solution is to commit your changes to a separate Homebrew branch, run `brew update`, and rebase your changes onto the updated master. You'll have to do this both for the main Homebrew repository in `/usr/local/` and the Homebrew science repository that contains OpenCV in `/usr/local/Library/Taps/homebrew/homebrew-science`, as follows:
+
+ cd /usr/local
+ git checkout -b caffe
+ git add .
+ git commit -m "Update Caffe dependencies to use libstdc++"
+ cd /usr/local/Library/Taps/homebrew/homebrew-science
+ git checkout -b caffe
+ git add .
+ git commit -m "Update Caffe dependencies"
+
+Then, whenever you want to update homebrew, switch back to the master branches, do the update, rebase the caffe branches onto master and fix any conflicts:
+
+ # Switch batch to homebrew master branches
+ cd /usr/local
+ git checkout master
+ cd /usr/local/Library/Taps/homebrew/homebrew-science
+ git checkout master
+
+ # Update homebrew; hopefully this works without errors!
+ brew update
+
+ # Switch back to the caffe branches with the forumlae that you modified earlier
+ cd /usr/local
+ git rebase master caffe
+ # Fix any merge conflicts and commit to caffe branch
+ cd /usr/local/Library/Taps/homebrew/homebrew-science
+ git rebase master caffe
+ # Fix any merge conflicts and commit to caffe branch
+
+ # Done!
+
+At this point, you should be running the latest Homebrew packages and your Caffe-related modifications will remain in place.
# Installation
-Prior to installing, it is best to read through this guide and take note of the details for your platform.
-We have installed Caffe on Ubuntu 14.04, Ubuntu 12.04, OS X 10.10, 10.9, and 10.8.
+Prior to installing, have a glance through this guide and take note of the details for your platform.
+We install and run Caffe on Ubuntu 14.04 and 12.04, OS X 10.10 / 10.9 / 10.8, and AWS.
+The official Makefile and `Makefile.config` build are complemented by an automatic CMake build from the community.
- [Prerequisites](#prerequisites)
- [Compilation](#compilation)
-- [Hardware questions](#hardware_questions)
+- [Hardware](#hardware)
+- Platforms: [Ubuntu guide](install_apt.html), [OS X guide](install_osx.html), and [RHEL / CentOS / Fedora guide](install_yum.html)
+
+When updating Caffe, it's best to `make clean` before re-compiling.
## Prerequisites
-Caffe depends on several software packages.
+Caffe has several dependencies.
+
+* [CUDA](https://developer.nvidia.com/cuda-zone) is required for GPU mode.
+ * library version 7.0 and the latest driver version are recommended, but 6.* is fine too
+ * 5.5, and 5.0 are compatible but considered legacy
+* [BLAS](http://en.wikipedia.org/wiki/Basic_Linear_Algebra_Subprograms) via ATLAS, MKL, or OpenBLAS.
+* [Boost](http://www.boost.org/) >= 1.55
+* [OpenCV](http://opencv.org/) >= 2.4 including 3.0
+* `protobuf`, `glog`, `gflags`
+* IO libraries `hdf5`, `leveldb`, `snappy`, `lmdb`
-* [CUDA](https://developer.nvidia.com/cuda-zone) library version 6.5 (recommended), 6.0, 5.5, or 5.0 and the latest driver version for CUDA 6 or 319.* for CUDA 5 (and NOT 331.*)
-* [BLAS](http://en.wikipedia.org/wiki/Basic_Linear_Algebra_Subprograms) (provided via ATLAS, MKL, or OpenBLAS).
-* [OpenCV](http://opencv.org/) (>= 2.4)
-* [Boost](http://www.boost.org/) (>= 1.55, although only 1.55 and 1.56 are tested)
-* `glog`, `gflags`, `protobuf`, `leveldb`, `snappy`, `hdf5`, `lmdb`
-* For the Python wrapper
- * `Python 2.7`, `numpy (>= 1.7)`, boost-provided `boost.python`
-* For the MATLAB wrapper
- * MATLAB with the `mex` compiler.
+Pycaffe and Matcaffe interfaces have their own natural needs.
-**cuDNN Caffe**: for fastest operation Caffe is accelerated by drop-in integration of [NVIDIA cuDNN](https://developer.nvidia.com/cudnn). To speed up your Caffe models, install cuDNN then uncomment the `USE_CUDNN := 1` flag in `Makefile.config` when installing Caffe. Acceleration is automatic.
+* For Python Caffe: `Python 2.7`, `numpy (>= 1.7)`, boost-provided `boost.python`
+* For MATLAB Caffe: MATLAB with the `mex` compiler.
+
+**cuDNN Caffe**: for fastest operation Caffe is accelerated by drop-in integration of [NVIDIA cuDNN](https://developer.nvidia.com/cudnn). To speed up your Caffe models, install cuDNN then uncomment the `USE_CUDNN := 1` flag in `Makefile.config` when installing Caffe. Acceleration is automatic. For now cuDNN v1 is integrated but see [PR #1731](https://github.com/BVLC/caffe/pull/1731) for v2.
**CPU-only Caffe**: for cold-brewed CPU-only Caffe uncomment the `CPU_ONLY := 1` flag in `Makefile.config` to configure and build Caffe without CUDA. This is helpful for cloud or cluster deployment.
For best performance, Caffe can be accelerated by [NVIDIA cuDNN](https://developer.nvidia.com/cudnn). Register for free at the cuDNN site, install it, then continue with these installation instructions. To compile with cuDNN set the `USE_CUDNN := 1` flag set in your `Makefile.config`.
Caffe requires BLAS as the backend of its matrix and vector computations.
-There are several implementations of this library.
-The choice is yours:
+There are several implementations of this library. The choice is yours:
* [ATLAS](http://math-atlas.sourceforge.net/): free, open source, and so the default for Caffe.
- + Ubuntu: `sudo apt-get install libatlas-base-dev`
- + CentOS/RHEL/Fedora: `sudo yum install atlas-devel`
- + OS X: already installed as the [Accelerate / vecLib Framework](https://developer.apple.com/library/mac/documentation/Darwin/Reference/ManPages/man7/Accelerate.7.html).
* [Intel MKL](http://software.intel.com/en-us/intel-mkl): commercial and optimized for Intel CPUs, with a free trial and [student](http://software.intel.com/en-us/intel-education-offerings) licenses.
1. Install MKL.
2. Set `BLAS := mkl` in `Makefile.config`
1. Install OpenBLAS
2. Set `BLAS := open` in `Makefile.config`
-### Python and/or MATLAB wrappers (optional)
+### Python and/or MATLAB Caffe (optional)
#### Python
You can install the dependencies with
- for req in $(cat requirements.txt); do sudo pip install $req; done
-
-but we highly recommend first installing the [Anaconda](https://store.continuum.io/cshop/anaconda/) Python distribution, which provides most of the necessary packages, as well as the `hdf5` library dependency.
+ for req in $(cat requirements.txt); do pip install $req; done
-For **Ubuntu**, if you use the default Python you will need to `sudo apt-get install` the `python-dev` package to have the Python headers for building the wrapper.
-
-For **Fedora**, if you use the default Python you will need to `sudo yum install` the `python-devel` package to have the Python headers for building the wrapper.
-
-For **OS X**, Anaconda is the preferred Python. If you decide against it, please use Homebrew -- but beware of potential linking errors!
+but we suggest first installing the [Anaconda](https://store.continuum.io/cshop/anaconda/) Python distribution, which provides most of the necessary packages, as well as the `hdf5` library dependency.
To import the `caffe` Python module after completing the installation, add the module directory to your `$PYTHONPATH` by `export PYTHONPATH=/path/to/caffe/python:$PYTHONPATH` or the like. You should not import the module in the `caffe/python/caffe` directory!
Install MATLAB, and make sure that its `mex` is in your `$PATH`.
-*Caffe's MATLAB interface works with versions 2012b, 2013a/b, and 2014a.*
-
-### The rest of the dependencies
-
-#### Linux
-
-On **Ubuntu**, most of the dependencies can be installed with
-
- sudo apt-get install libprotobuf-dev libleveldb-dev libsnappy-dev libopencv-dev libboost-all-dev libhdf5-serial-dev
-
-and for **Ubuntu 14.04** the rest of the dependencies can be installed with
-
- sudo apt-get install libgflags-dev libgoogle-glog-dev liblmdb-dev protobuf-compiler
-
-Keep reading to find out how to manually build and install the Google flags library, Google logging library and LMDB on **Ubuntu 12.04**.
-
-On **CentOS / RHEL / Fedora**, most of the dependencies can be installed with
-
- sudo yum install protobuf-devel leveldb-devel snappy-devel opencv-devel boost-devel hdf5-devel
-
-The Google flags library, Google logging library and LMDB already made their ways into newer versions of **CentOS / RHEL / Fedora** so it is better to first attempt to install them using `yum`
-
- sudo yum install gflags-devel glog-devel lmdb-devel
-
-**Finally** in case you couldn't find those extra libraries mentioned above in your distribution's repositories, here are the instructions to follow for manually building and installing them on **Ubuntu 12.04 / CentOS / RHEL / Fedora** (or practically on any Linux distribution)
-
- # glog
- wget https://google-glog.googlecode.com/files/glog-0.3.3.tar.gz
- tar zxvf glog-0.3.3.tar.gz
- cd glog-0.3.3
- ./configure
- make && make install
- # gflags
- wget https://github.com/schuhschuh/gflags/archive/master.zip
- unzip master.zip
- cd gflags-master
- mkdir build && cd build
- export CXXFLAGS="-fPIC" && cmake .. && make VERBOSE=1
- make && make install
- # lmdb
- git clone git://gitorious.org/mdb/mdb.git
- cd mdb/libraries/liblmdb
- make && make install
-
-Note that glog does not compile with the most recent gflags version (2.1), so before that is resolved you will need to build with glog first.
-
-#### OS X
-
-On **OS X**, we highly recommend using the [Homebrew](http://brew.sh/) package manager, and ideally starting from a clean install of the OS (or from a wiped `/usr/local`) to avoid conflicts.
-In the following, we assume that you're using Anaconda Python and Homebrew.
-
-To install the OpenCV dependency, we'll need to provide an additional source for Homebrew:
-
- brew tap homebrew/science
-
-If using Anaconda Python, a modification is required to the OpenCV formula.
-Do `brew edit opencv` and change the lines that look like the two lines below to exactly the two lines below.
-
- -DPYTHON_LIBRARY=#{py_prefix}/lib/libpython2.7.dylib
- -DPYTHON_INCLUDE_DIR=#{py_prefix}/include/python2.7
-
-**NOTE**: We find that everything compiles successfully if `$LD_LIBRARY_PATH` is not set at all, and `$DYLD_FALLBACK_LIBRARY_PATH` is set to to provide CUDA, Python, and other relevant libraries (e.g. `/usr/local/cuda/lib:$HOME/anaconda/lib:/usr/local/lib:/usr/lib`).
-In other `ENV` settings, things may not work as expected.
-
-**NOTE**: There is currently a conflict between boost 1.56 and CUDA in some configurations. Check the [conflict description](https://github.com/BVLC/caffe/issues/1193#issuecomment-57491906) and try downgrading to 1.55 or upgrading to 1.57.
-
-#### 10.8-specific Instructions
-
-Simply run the following:
-
- brew install --build-from-source boost boost-python
- brew install --with-python protobuf
- for x in snappy leveldb gflags glog szip lmdb homebrew/science/opencv; do brew install $x; done
-
-Building boost from source is needed to link against your local Python (exceptions might be raised during some OS X installs, but **ignore** these and continue). If you do not need the Python wrapper, simply doing `brew install boost` is fine.
-
-**Note** that the HDF5 dependency is provided by Anaconda Python in this case.
-If you're not using Anaconda, include `hdf5` in the list above.
-
-#### 10.10- and 10.9-specific Instructions
-
-In OS X 10.9+, clang++ is the default C++ compiler and uses `libc++` as the standard library.
-However, NVIDIA CUDA (even version 6.0) currently links only with `libstdc++`.
-This makes it necessary to change the compilation settings for each of the dependencies.
-
-We do this by modifying the Homebrew formulae before installing any packages.
-Make sure that Homebrew doesn't install any software dependencies in the background; all packages must be linked to `libstdc++`.
-
-The prerequisite Homebrew formulae are
-
- boost snappy leveldb protobuf gflags glog szip lmdb homebrew/science/opencv
-
-For each of these formulas, `brew edit FORMULA`, and add the ENV definitions as shown:
-
- def install
- # ADD THE FOLLOWING:
- ENV.append "CXXFLAGS", "-stdlib=libstdc++"
- ENV.append "CFLAGS", "-stdlib=libstdc++"
- ENV.append "LDFLAGS", "-stdlib=libstdc++ -lstdc++"
- # The following is necessary because libtool likes to strip LDFLAGS:
- ENV["CXX"] = "/usr/bin/clang++ -stdlib=libstdc++"
- ...
-
-To edit the formulae in turn, run
-
- for x in snappy leveldb protobuf gflags glog szip boost boost-python lmdb homebrew/science/opencv; do brew edit $x; done
-
-After this, run
-
- for x in snappy leveldb gflags glog szip lmdb homebrew/science/opencv; do brew uninstall $x; brew install --build-from-source --fresh -vd $x; done
- brew uninstall protobuf; brew install --build-from-source --with-python --fresh -vd protobuf
- brew install --build-from-source --fresh -vd boost boost-python
-
-**Note** that `brew install --build-from-source --fresh -vd boost` is fine if you do not need the Caffe Python wrapper.
-
-**Note** that the HDF5 dependency is provided by Anaconda Python in this case.
-If you're not using Anaconda, include `hdf5` in the list above.
-
-**Note** that in order to build the Caffe Python wrappers you must install `boost` and `boost-python`:
-
- brew install --build-from-source --fresh -vd boost boost-python
-
-**Note** that Homebrew maintains itself as a separate git repository and making the above `brew edit FORMULA` changes will change files in your local copy of homebrew's master branch. By default, this will prevent you from updating Homebrew using `brew update`, as you will get an error message like the following:
-
- $ brew update
- error: Your local changes to the following files would be overwritten by merge:
- Library/Formula/lmdb.rb
- Please, commit your changes or stash them before you can merge.
- Aborting
- Error: Failure while executing: git pull -q origin refs/heads/master:refs/remotes/origin/master
-
-One solution is to commit your changes to a separate Homebrew branch, run `brew update`, and rebase your changes onto the updated master. You'll have to do this both for the main Homebrew repository in `/usr/local/` and the Homebrew science repository that contains OpenCV in `/usr/local/Library/Taps/homebrew/homebrew-science`, as follows:
-
- cd /usr/local
- git checkout -b caffe
- git add .
- git commit -m "Update Caffe dependencies to use libstdc++"
- cd /usr/local/Library/Taps/homebrew/homebrew-science
- git checkout -b caffe
- git add .
- git commit -m "Update Caffe dependencies"
-
-Then, whenever you want to update homebrew, switch back to the master branches, do the update, rebase the caffe branches onto master and fix any conflicts:
-
- # Switch batch to homebrew master branches
- cd /usr/local
- git checkout master
- cd /usr/local/Library/Taps/homebrew/homebrew-science
- git checkout master
-
- # Update homebrew; hopefully this works without errors!
- brew update
-
- # Switch back to the caffe branches with the forumlae that you modified earlier
- cd /usr/local
- git rebase master caffe
- # Fix any merge conflicts and commit to caffe branch
- cd /usr/local/Library/Taps/homebrew/homebrew-science
- git rebase master caffe
- # Fix any merge conflicts and commit to caffe branch
-
- # Done!
-
-At this point, you should be running the latest Homebrew packages and your Caffe-related modifications will remain in place.
+*Caffe's MATLAB interface works with versions 2014a/b, 2013a/b, and 2012b.*
#### Windows
## Compilation
-Now that you have the prerequisites, edit your `Makefile.config` to change the paths for your setup (you should especially uncomment and set `BLAS_LIB` accordingly on distributions like **CentOS / RHEL / Fedora** where ATLAS is installed under `/usr/lib[64]/atlas`)
-The defaults should work, but uncomment the relevant lines if using Anaconda Python.
+Now that you have the prerequisites, edit your `Makefile.config` to change the paths for your setup The defaults should work, but uncomment the relevant lines if using Anaconda Python.
cp Makefile.config.example Makefile.config
# Adjust Makefile.config (for example, if using Anaconda Python)
make test
make runtest
-To compile with cuDNN acceleration, you should uncomment the `USE_CUDNN := 1` switch in `Makefile.config`.
-
-If there is no GPU in your machine, you should switch to CPU-only Caffe by uncommenting `CPU_ONLY := 1` in `Makefile.config`.
+- For cuDNN acceleration, you should uncomment the `USE_CUDNN := 1` switch in `Makefile.config`.
+- For CPU-only Caffe, uncomment `CPU_ONLY := 1` in `Makefile.config`.
To compile the Python and MATLAB wrappers do `make pycaffe` and `make matcaffe` respectively.
Be sure to set your MATLAB and Python paths in `Makefile.config` first!
-*Distribution*: run `make distribute` to create a `distribute` directory with all the Caffe headers, compiled libraries, binaries, etc. needed for distribution to other machines.
+**Distribution**: run `make distribute` to create a `distribute` directory with all the Caffe headers, compiled libraries, binaries, etc. needed for distribution to other machines.
-*Speed*: for a faster build, compile in parallel by doing `make all -j8` where 8 is the number of parallel threads for compilation (a good choice for the number of threads is the number of cores in your machine).
+**Speed**: for a faster build, compile in parallel by doing `make all -j8` where 8 is the number of parallel threads for compilation (a good choice for the number of threads is the number of cores in your machine).
Now that you have installed Caffe, check out the [MNIST tutorial](gathered/examples/mnist.html) and the [reference ImageNet model tutorial](gathered/examples/imagenet.html).
### CMake Compilation
-In lieu of manually editing `Makefile.config` to configure the build, Caffe offers an unofficial CMake build thanks to @Nerei, @akosiorek, and other members of the community.
-It requires CMake version >= 2.8.7.
-The basic installation steps are as follows:
+In lieu of manually editing `Makefile.config` to configure the build, Caffe offers an unofficial CMake build thanks to @Nerei, @akosiorek, and other members of the community. It requires CMake version >= 2.8.7.
+The basic steps are as follows:
mkdir build
cd build
make all
make runtest
-See [PR #1667](https://github.com/BVLC/caffe/pull/1667) for details.
-
-#### Ubuntu 12.04
-
-Note that in Ubuntu 12.04, Aptitude will install version CMake 2.8.7 by default, which is not supported by Caffe's CMake build (requires at least 2.8.8).
-As a workaround, if you are using Ubuntu 12.04 you can try the following steps to install (or upgrade to) CMake 2.8.9:
-
- sudo add-apt-repository ppa:ubuntu-sdk-team/ppa -y
- sudo apt-get -y update
- sudo apt-get install cmake
+See [PR #1667](https://github.com/BVLC/caffe/pull/1667) for options and details.
-## Hardware Questions
+## Hardware
-**Laboratory Tested Hardware**: Berkeley Vision runs Caffe with K40s, K20s, and Titans including models at ImageNet/ILSVRC scale. We also run on GTX series cards and GPU-equipped MacBook Pros. We have not encountered any trouble in-house with devices with CUDA capability >= 3.0. All reported hardware issues thus-far have been due to GPU configuration, overheating, and the like.
+**Laboratory Tested Hardware**: Berkeley Vision runs Caffe with K40s, K20s, and Titans including models at ImageNet/ILSVRC scale. We also run on GTX series cards (980s and 770s) and GPU-equipped MacBook Pros. We have not encountered any trouble in-house with devices with CUDA capability >= 3.0. All reported hardware issues thus-far have been due to GPU configuration, overheating, and the like.
**CUDA compute capability**: devices with compute capability <= 2.0 may have to reduce CUDA thread numbers and batch sizes due to hardware constraints. Your mileage may vary.
Once installed, check your times against our [reference performance numbers](performance_hardware.html) to make sure everything is configured properly.
-Refer to the project's issue tracker for [hardware/compatibility](https://github.com/BVLC/caffe/issues?labels=hardware%2Fcompatibility&page=1&state=open).
+Ask hardware questions on the [caffe-users group](https://groups.google.com/forum/#!forum/caffe-users).
projects / platform / upstream / caffe.git / commitdiff