Build Script Issues #1
Description
Good news first. I am able to successfully build on Ubuntu 13.04.
I did, however, run into a few issues with the build script.
echoing out the wget progress for the Nest toolchain might be a good idea perhaps?
On my rather slow connection it takes a while and gives the impression that the script is hanging. Something like:
wget http://files.chumby.com/toolchain/arm-2008q3-72-arm-none-linux-gnueabi-i686-pc-linux-gnu.tar.bz2 2>&3
would do the trick, I think, though the output could be cleaned up with some grep or awk. curl also makes this easier but wget is nice too : )
It might also be worth doing a
if [ ! -f arm-2008q3-72-arm-none-linux-gnueabi-i686-pc-linux-gnu.tar.bz2]
as the script might have a bit of trouble recovering from incomplete wgets on subsequent runs and this would prevent the need to download an 80.5M file every time we try to build, assuming the rm gets commented out. Either way is cool really, just a thought.
Setting of the PATH environmental variable failed for me, though adding an export resolved the issue.
Even though the path to the toolchain was in $PATH, I kept getting arm-none-linux-gnueabi-gcc (or whatever) not found errors.
I solved this by storing the path to the toolchain in a local variable and passing it to the relevant make commands. i.e. -
toolchain_path=$(pwd)/arm-2008q3/bin/arm-none-linux-gnueabi-
make ARCH=arm CROSS_COMPILE=$toolchain_path distclean
Finally, I had buckets of permissions issues. sudo fixed my problems but I understand that it might not be a good idea or even possible to use sudo make on many systems.
Perhaps running a permissions check or chown recursively over the directory structure would be beneficial?
Admittedly, there are probably better ways to solve some of these issues than the ones I mentioned, but the quick and dirty fixes got the job done for me.
Fantastic work guys.