Short version foot note: do you want to avoid wasting time? Set up a Debian VM. It's the only way we can be sure everyone has a successful experience with openwrt-yun.Longer version foot note: compiling openwrt-yun is not difficult but takes patience. It's highly suggested that you strictly follow the instructions (use a debian wheezy, real or running inside virtualbox or kvm, not your own distro) as many different distributions may need specific tweaks that we are unlikely to document since they will be unsupported.
git checkout -b release 1.0.0
git checkout -b f58425387a0ce96bb709489f526dfaf0dae2e1afgit pull origin f58425387a0ce96bb709489f526dfaf0dae2e1af
This brings to light a fact I did not realize even though it is obvious. When you pull from the git https://github.com/arduino/openwrt-yun you get the latest, greatest, perhaps buggiest thing available.
apt-get install git subversion build-essential asciidoc \ fastjar flex gawk libgtk2.0-dev intltool zlib1g-dev \ genisoimage libncurses5-dev libssl-dev ruby sdcc unzip \ bison libboost-dev libxml-parser-perl libusb-dev bin86 \ bcc sharutils openjdk-7-jdk mercurial cvs bzr npm
Reading package lists... DoneBuilding dependency treeReading state information... DoneE: unable to locate package npm
Wow! Buggiest!I know (and sadly accepted) that openwrt build sometime fails, but just really sometime. May you elaborate? Why buggiest?
Quote from: Federico Fissore on May 16, 2014, 04:28 pmWow! Buggiest!I know (and sadly accepted) that openwrt build sometime fails, but just really sometime. May you elaborate? Why buggiest?Because it is the latest and greatest! It's the nature of the beast. If you want to be on the bleeding edge you need to be prepared for some issues.While I envy some of the things you get play with, some of the comments I have seen make me hope you wear asbestos underwear. I am extremely impressed with the yun and what the team has put together.I also added some emphasis to the perhaps in the original post, it's not ALWAYS the buggiest.
Got the result:Code: [Select]Reading package lists... DoneBuilding dependency treeReading state information... DoneE: unable to locate package npm
2) has the speed of the bridge been improved in anyway? If not, how can it be?