Jump to content

Armbian 5.20 / u-boot compile failure


Recommended Posts

I'm just starting out with Armbian development, and the most recent "stable" version (5.20, v2016.09) doesn't
 compile. Is this supposed to work?

 

olaf@tackd:~$ mkdir routertest
olaf@tackd:~$ cd routertest/
olaf@tackd:~/routertest$
olaf@tackd:~/routertest$ git clone -b v2016.09 https://github.com/igorpecovnik/lib
Cloning into 'lib'...
remote: Counting objects: 19756, done.
remote: Compressing objects: 100% (155/155), done.
remote: Total 19756 (delta 75), reused 0 (delta 0), pack-reused 19601
Receiving objects: 100% (19756/19756), 173.96 MiB | 1003.00 KiB/s, done.
Resolving deltas: 100% (12762/12762), done.
Checking connectivity... done.
Note: checking out '4c54309b7b1c681817dfc733d26ccf56b08aedf3'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b <new-branch-name>

olaf@tackd:~/routertest$
olaf@tackd:~/routertest$ cat >Vagrantfile <<EOF
Vagrant.configure(2) do |config|
  config.vm.box = "ubuntu/xenial64"
  config.vm.box_check_update = true
  config.vm.network "public_network"
  config.vm.provider "virtualbox" do |vb|
    vb.memory = "4096"
    vb.cpus = "1"
  end
end
EOF

olaf@tackd:~/routertest$
olaf@tackd:~/routertest$ vagrant up
==> default: Importing base box 'ubuntu/xenial64'...
==> default: Matching MAC address for NAT networking...
==> default: Checking if box 'ubuntu/xenial64' is up to date...
==> default: Setting the name of the VM: routertest_default_1489208867928_73453
.....
==> default: Mounting shared folders...
    default: /vagrant => /home/olaf/routertest
olaf@tackd:~/routertest$
olaf@tackd:~/routertest$ vagrant ssh
Welcome to Ubuntu 16.04.2 LTS (GNU/Linux 4.4.0-66-generic x86_64)

 * Documentation:  https://help.ubuntu.com
 * Management:     https://landscape.canonical.com
 * Support:        https://ubuntu.com/advantage

  Get cloud support with Ubuntu Advantage Cloud Guest:
    http://www.ubuntu.com/business/services/cloud

0 packages can be updated.
0 updates are security updates.


ubuntu@ubuntu-xenial:~$ sudo su
root@ubuntu-xenial:/home/ubuntu# cd /vagrant/
root@ubuntu-xenial:/vagrant# ls
Vagrantfile  lib  ubuntu-xenial-16.04-cloudimg-console.log
root@ubuntu-xenial:/vagrant#
root@ubuntu-xenial:/vagrant# cat >compile.sh <<'EOF'
> #!/bin/bash
>
> KERNEL_ONLY=""                          # leave empty to select each time, set to "yes" or "no" to skip dialog prompt
> KERNEL_CONFIGURE="no"                   # change provided kernel configuration
> CLEAN_LEVEL="make,debs"                 # comma-separated list of clean targets: "make" = make clean for selected kernel and u-boot,
>                                         # "debs" = delete packages in "./output/debs" for current branch and family,
>                                         # "alldebs" - delete all packages in "./output/debs", "images" = delete "./output/images",
>                                         # "cache" = delete "./output/cache", "sources" = delete "./sources"
>
> DEST_LANG="en_US.UTF-8"                 # sl_SI.UTF-8, en_US.UTF-8
>
> # advanced
> KERNEL_KEEP_CONFIG="no"                 # do not overwrite kernel config before compilation
> EXTERNAL="yes"                          # build and install extra applications and drivers
> EXTERNAL_NEW="prebuilt"                 # compile and install or install prebuilt additional packages
> DEBUG_MODE="no"                         # wait that you make changes to uboot and kernel source and creates patches
> FORCE_CHECKOUT="yes"                    # ignore manual changes to source
> BUILD_ALL="no"                          # cycle through available boards and make images or kernel/u-boot packages.
>                                         # set KERNEL_ONLY to "yes" or "no" to build all packages/all images
>
> BOARD="bananapi"                                                # bananapi
> BRANCH="default"                                                # default=3.4.x, mainline=next
> RELEASE="jessie"                                                # jessie, wheezy or trusty
>
> KERNEL_ONLY="no"                                # leave empty to select each time, set to "yes" or "no" to skip dialog prompt
> KERNEL_CONFIGURE="no"                   # change provided kernel configuration
> KERNEL_CLEAN="yes"                                              # run MAKE clean before kernel compilation
> CLEAN_LEVEL="make,debs,oldcache"        # comma-separated list of clean targets: "make" = make clean for selected kernel and u-boot,
>                                         # "debs" = delete packages in "./output/debs" for current branch and family,
>                                         # "alldebs" = delete all packages in "./output/debs", "images" = delete "./output/images",
>                                         # "cache" = delete "./output/cache", "sources" = delete "./sources"
>                                         # "oldcache" = remove old cached rootfs except for the newest 6 files
>
> DEST_LANG="en_US.UTF-8"                 # sl_SI.UTF-8, en_US.UTF-8
>
> # advanced
> KERNEL_KEEP_CONFIG="no"                 # do not overwrite kernel config before compilation
> EXTERNAL="yes"                          # build and install extra applications and drivers
> EXTERNAL_NEW="prebuilt"                 # compile and install or install prebuilt additional packages
> FBTFT="no"                                                   # https://github.com/notro/fbtft
> CREATE_PATCHES="no"                     # wait that you make changes to uboot and kernel source and creates patches
> FORCE_CHECKOUT="yes"                    # ignore manual changes to source
> BUILD_ALL="no"                          # cycle through available boards and make images or kernel/u-boot packages.
>                                         # set KERNEL_ONLY to "yes" or "no" to build all packages/all images
>
> BETA=""                                 # set yes to add subrevision with tomorrow's date. For internal use.
> MULTITHREAD=""                          # build n images at once. For internal use.
> BUILD_DESKTOP=no
>
> PROGRESS_DISPLAY=plain  # suppress ascii UIs
> PROGRESS_LOG_TO_FILE=yes
>
>
> LIB_TAG=""                              # empty for latest version,
>                                         # one of listed here: https://github.com/igorpecovnik/lib/tags for stable versions,
>                                         # or commit hash
>
>
> SRC=$(pwd)
>
> source $SRC/lib/main.sh
>
> [[ $(type -t run_after_build) == function ]] && run_after_build || true
> # VERSION=23
> EOF
root@ubuntu-xenial:/vagrant#
root@ubuntu-xenial:/vagrant# chmod +x compile.sh
root@ubuntu-xenial:/vagrant# ./compile.sh
[ o.k. ] Preparing [ host ]
[ .... ] Installing package [ dialog ]
[ o.k. ] Build host OS release [ xenial ]
Hit:1 http://archive.ubuntu.com/ubuntu xenial InRelease
Get:2 http://security.ubuntu.com/ubuntu xenial-security InRelease [102 kB]
Get:3 http://archive.ubuntu.com/ubuntu xenial-updates InRelease [102 kB]
Get:4 http://archive.ubuntu.com/ubuntu xenial-backports InRelease [102 kB]
Get:5 http://security.ubuntu.com/ubuntu xenial-security/main Sources [62.4 kB]
Get:6 http://security.ubuntu.com/ubuntu xenial-security/restricted Sources [2288 B]
.....
[ o.k. ] Downloading toolchain [ gcc-linaro-5.2-2015.11-2-x86_64_arm-linux-gnueabihf ]
######################################################################## 100.0%
######################################################################## 100.0%
[ .... ] Verifying
[ .... ] Extracting
[ o.k. ] Download complete
[ o.k. ] Downloading toolchain [ gcc-linaro-arm-linux-gnueabihf-4.8-2014.04_linux ]

curl: (22) The requested URL returned error: 404 NOT FOUND

curl: (22) The requested URL returned error: 404 NOT FOUND
[ .... ] Verifying
grep: gcc-linaro-arm-linux-gnueabihf-4.8-2014.04_linux.tar.xz.asc: No such file or directory
md5sum: gcc-linaro-arm-linux-gnueabihf-4.8-2014.04_linux.tar.xz.asc: No such file or directory
[ warn ] Verification failed
rm: cannot remove '/vagrant/userpatches/readme.txt': No such file or directory
/vagrant/lib/general.sh: line 573: 1705647038464
1705647038464 / 1073741824 : syntax error in expression (error token is "1705647038464 / 1073741824 ")
[ o.k. ] Starting Armbian build script [ @host ]
[ o.k. ] Syncing clock [ host ]
[ o.k. ] Downloading sources
.....
[ o.k. ] Compiling uboot [ 2016.09 ]
[ o.k. ] Compiler version [ arm-linux-gnueabihf-gcc 5.2.1 ]
  HOSTCC  scripts/basic/fixdep
  HOSTCC  scripts/kconfig/conf.o
  SHIPPED scripts/kconfig/zconf.tab.c
  SHIPPED scripts/kconfig/zconf.lex.c
  SHIPPED scripts/kconfig/zconf.hash.c
  HOSTCC  scripts/kconfig/zconf.tab.o
.....
  OBJCOPY spl/u-boot-spl-nodtb.bin
  COPY    spl/u-boot-spl.bin
  CFG     spl/u-boot-spl.cfg
  MKSUNXI spl/sunxi-spl.bin
  OBJCOPY u-boot-nodtb.bin
  CAT     u-boot-dtb.bin
  COPY    u-boot.bin
  MKIMAGE u-boot.img
./tools/mkimage: Can't map u-boot.img: Invalid argument
make: *** [u-boot.img] Error 1
Makefile:927: recipe for target 'u-boot.img' failed
[ error ] ERROR in function compile_uboot [ common.sh:96 ]
[ error ] U-boot file not found [ u-boot-sunxi-with-spl.bin ]
[ o.k. ] Process terminated
root@ubuntu-xenial:/vagrant#


Again, is this supposed to work? Is the 404 and the syntax error relevant to the failure?

 

(output directory contents attached)

output.tgz

Link to comment
Share on other sites

Those older building environment are not very well supported. Just go for latest version - we are doing daily builds with exact this script and we notice quickly if it breaks.

 

It should be stable if you choose stable boards / default kernels and Ubuntu Xenial desktop if you need a desktop.

 

 

Link to comment
Share on other sites

OK thanks, building the master worked.

 

Quote

Those older building environment are not very well supported.

 

Why is this btw? Would the build of the tagged version have succeeded back when it was new? I.e. do we have repeatable builds to some degree?

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines