quentin Posted April 12, 2016 Posted April 12, 2016 Hi, I own a Orange PI One and I wanted to create a compile environment in a virtualbox as I did not find any available. So I followed the instructions found here: http://www.armbian.com/using-armbian-tools/ 1) downloaded "ubuntu-14.04.4-server-amd64.iso" 2) create a new virtual box image (ubuntu 64bit) 3) Execute the following command: apt-get -y -qq install git git clone --depth 1 https://github.com/igorpecovnik/lib cp lib/compile.sh . sudo ./compile.sh The process end with the following lines: [ o.k. ] Building deb [ linux-u-boot-orangepih3-5.07-armhf.deb ] [ error ] ERROR in function compilte_uboot [ common.sh:155 ] [ error ] Building u-boot failed, check configuration [ o.k. ] Process terminated If any one could help me with this issue (and/or have any link to a compile environment virtualbox), I would be grateful.
zador.blood.stained Posted April 12, 2016 Posted April 12, 2016 What kernel branch did you select(default/next/dev)? It must be "default" based on u-boot file name. Can you repeat compilation process with PROGRESS_LOG_TO_FILE=yes added to compile.sh and then post contents of "output/debug/compilation.log" somewhere (like pastebin.com)?
quentin Posted April 12, 2016 Author Posted April 12, 2016 The "output/debug/compilation.log" file is emptyoutput.log : http://pastebin.com/Xip3uF4D install.log : http://pastebin.com/8V9Jnht1
tkaiser Posted April 12, 2016 Posted April 12, 2016 One patch is failing, what happens when you do a touch /home/armbian/ArmbianGit/userpatches/u-boot/u-boot-default/u-boot-02-support-cheap-mmc.patch and retry then?
zador.blood.stained Posted April 12, 2016 Posted April 12, 2016 If these logs are from second compilation attempt, then problem is in host dependencies installation (aptly package) - it already happened before when aptly repository signing key expired. WARNING: The following packages cannot be authenticated! aptly @quentin You can try removing "aptly" from general.sh, line 288 304 and repeat compilation attempt. Alternatively you can try using Ubuntu Xenial (16.04 beta ) as your build host instead of 14.04.
quentin Posted April 12, 2016 Author Posted April 12, 2016 One patch is failing, what happens when you do a touch /home/armbian/ArmbianGit/userpatches/u-boot/u-boot-default/u-boot-02-support-cheap-mmc.patch and retry then? Only difference is: /home/armbian/ArmbianGit/lib/patch/u-boot/u-boot-default/u-boot-02-support-cheap-mmc.patch u-boot-default 2016.03 patch unexpectedly ends in middle of line Displaying message: ... u-boot-02-support-cheap-mmc.patch succeeded info became: Displaying message: ... u-boot-02-support-cheap-mmc.patch skipped info
quentin Posted April 12, 2016 Author Posted April 12, 2016 If these logs are from second compilation attempt, then problem is in host dependencies installation (aptly package) - it already happened before when aptly repository signing key expired. WARNING: The following packages cannot be authenticated! aptly @quentin You can try removing "aptly" from general.sh, line 288 304 and repeat compilation attempt. Alternatively you can try using Ubuntu Xenial (16.04 beta ) as your build host instead of 14.04. Yes I made the modification on the line 304 as it was the closest It seems to correct the issue as the compilation is progressing. Thanks,
Recommended Posts