summaryrefslogtreecommitdiff
path: root/BUILD_GUIDE.md
diff options
context:
space:
mode:
authorAndrew Pritchard2016-03-28 08:39:39 -0700
committerAndrew Pritchard2016-03-28 08:39:39 -0700
commit1fd9dbdbe9e7a819a7dae50d9b745640435e0e13 (patch)
treea39eccbca99d2fddc515bc77c19be2ad174086d6 /BUILD_GUIDE.md
parent80eefb09ac5de95a6977702b4014d4b4d79a5d7d (diff)
Add avr-libc to the Debian build dependencies.
Without avr-libc the build fails trying to #include_next a header from the standard library, which of course doesn't exist.
Diffstat (limited to 'BUILD_GUIDE.md')
-rw-r--r--BUILD_GUIDE.md6
1 files changed, 3 insertions, 3 deletions
diff --git a/BUILD_GUIDE.md b/BUILD_GUIDE.md
index 81c3ec44f..e8b242e4e 100644
--- a/BUILD_GUIDE.md
+++ b/BUILD_GUIDE.md
@@ -25,12 +25,12 @@ You can also try these instructions:
3. Install [DFU-Programmer][dfu-prog].
### Linux
-Install AVR GCC and dfu-progammer with your favorite package manager.
+Install AVR GCC, AVR libc, and dfu-progammer with your favorite package manager.
Debian/Ubuntu example:
sudo apt-get update
- sudo apt-get install gcc-avr dfu-programmer
+ sudo apt-get install gcc-avr avr-libc dfu-programmer
### Vagrant
If you have any problems building the firmware, you can try using a tool called Vagrant. It will set up a virtual computer with a known configuration that's ready-to-go for firmware building. OLKB does NOT host the files for this virtual computer. Details on how to set up Vagrant are in the [VAGRANT_GUIDE file](VAGRANT_GUIDE.md).
@@ -52,4 +52,4 @@ If you have any problems building the firmware, you can try using a tool called
## Troubleshooting
1. Try running `make clean` if the make command fails.
- WIP \ No newline at end of file
+ WIP