You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: GUIDE.md
+29-22Lines changed: 29 additions & 22 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -78,6 +78,7 @@ Now move into the new `protobuf` directory, configure it, and `make` it. _Note:
78
78
79
79
```shell
80
80
cd protobuf
81
+
git checkout d5fb408d
81
82
./autogen.sh
82
83
./configure --prefix=/usr
83
84
make -j 4
@@ -102,11 +103,11 @@ cd ../..
102
103
git clone https://github.com/bazelbuild/bazel.git
103
104
```
104
105
105
-
Next, go into the new `bazel` direcotry and immediately checkout version 0.1.4 of Bazel._Note: we do this because a hack-y workaround we do later on doesn't work for the most recent version of Bazel. If you have instructions for building Bazel 2.0 or later on Raspberry Pi, please send a pull request!_
106
+
Next, go into the new `bazel` direcotry and immediately checkout version 0.2.1 of Bazel.
106
107
107
108
```shell
108
109
cd bazel
109
-
git checkout tags/0.1.4
110
+
git checkout 0.2.1
110
111
```
111
112
112
113
After that, copy the two Protobuf files mentioned earlier into the Bazel project. Note the naming of the files in this step- it must be precise.
Before building Bazel, we need to set the `javac` maximum heap size for this job, or else we'll get an OutOfMemoryError. To do this, we need to make a small addition to `bazel/scripts/bootstrap/compile.sh`. (Shout-out to @SangManLINUX for [pointing this out.](https://github.com/samjabrahams/tensorflow-on-raspberry-pi/issues/5#issuecomment-210965695).
121
+
122
+
```shell
123
+
nano scripts/bootstrap/compile.sh
124
+
```
125
+
126
+
Move down to line 128, where you'll see the following block of code:
127
+
128
+
```shell
129
+
run "${JAVAC}" -classpath "${classpath}" -sourcepath "${sourcepath}" \
Now we can build Bazel! _Note: this also takes some time._
120
143
121
144
```shell
@@ -129,7 +152,7 @@ sudo mkdir /usr/local/bin
129
152
sudo cp output/bazel /usr/local/bin/bazel
130
153
```
131
154
132
-
To make sure it's working properly, run `bazel` on the command line and verify it prints help text.
155
+
To make sure it's working properly, run `bazel` on the command line and verify it prints help text. Note: this may take 15-30 seconds to run, so be patient!
_Note: if you're looking to build to a specific version or commit of TensorFlow (as opposed to the HEAD at master), you should `git checkout` it now`
266
+
242
267
Once in the directory, we have to write a nifty one-liner that is incredibly important. The next line goes through all files and changes references of 64-bit program implementations (which we don't have access to) to 32-bit implementations. Neat!
If all has gone according to plan, you should be the proud owner of a TensorFlow-capable Raspberry Pi! But before removing your swap drive, you may want to consider building one of the optional TensorFlow components, such as the [initial distributed runtime](https://github.com/tensorflow/tensorflow/tree/master/tensorflow/core/distributed_runtime). Building it is a breeze (relatively):
_This section will attempt to maintain a list of remedies for problems that may occur while installing from `pip`_
39
39
40
-
#### "tensorflow-0.7.1-cp27-none-linux_armv7l.whl is not a supported wheel on this platform."
40
+
#### "tensorflow-0.8.0rc0-cp27-none-linux_armv7l.whl is not a supported wheel on this platform."
41
41
42
42
This wheel was built with Python 2.7, and can't be installed with a version of `pip` that uses Python 3. If you get the above message, try running the following command instead:
0 commit comments