Probleme mit ./buildscript build - Wer kann helfen?

Christian Dresel fff at chrisi01.de
Di Jul 31 23:40:15 CEST 2018


Hi

Sry kurz angebunden am Handy:

Statt

./buildscript build

Mal mit

./buildscript build debug

Bauen, dann sollten mehr Fehler kommen, und man erkennt besser woran es scheitert. Ist U.u. eine sehr lange Liste dann und man muss bisschen suchen

Mfg

Christian

Am 31. Juli 2018 23:27:55 MESZ schrieb Christoph Stitz <info at steampixel.de>:
>Hey,
>
>ich habe mir eine VM auf Basis von ubuntu/xenial64 eingerichtet um
>meine
>Freifunk-Router (TP-Link-WR1043N) automatisch mit einer neuen Firmware
>zu versorgen. Dazu habe ich versucht mich so weit wie möglich an die
>Anleitung hier zu halten: 
>https://wiki.freifunk-franken.de/w/FirmwareEntwicklung
>
>Die Provisionierung für die Ubuntu-VM sieht wie folgt aus:
>
>/# update//
>//apt-get update//
>//
>//# install dependencys//
>//apt-get install -y zlib1g-dev lua5.2 build-essential unzip
>libncurses-dev gawk subversion git realpath libssl-dev//
>//
>//# install python 2.x//
>//apt-get install -y python-minimal/
>
>Innerhalb der VM versuche ich dann mit einem Script die Firmware zu
>bauen:
>
>/# Clone repository if not exist//
>//# If exists pull//
>//if cd ~/firmware; then git pull; else git clone
>https://github.com/FreifunkFranken/firmware.git ~/firmware; fi//
>//
>//cd ~/firmware//
>//
>//# Mit Hilfe der Community-Files werden Parameter, wie die ESSID, der
>Kanal sowie z.B. die Netmon-IP gesetzt. //
>//# Diese Einstellungen sind Community weit einheitlich und müssen
>i.d.R. nicht geändert werden. //
>//./buildscript selectcommunity community/franken.cfg//
>//
>//# Je nach dem, für welche Hardware die Firmware gebaut werden soll
>muss das BSP gewählt werden: //
>//./buildscript selectbsp bsp/board_ar71xx.bsp//
>//
>//# Prepare//
>//./buildscript prepare//
>//
>//# Build//
>//./buildscript build//
>//
>//cd ../
>
>Nachdem ich einen Kaffee trinken war bekomme ich die folgende
>Fehlermeldung. Scheinbar werden einige Files nicht gefunden:
>
>...
>make[3] -C /home/vagrant/firmware/src/packages/fff/fff compile
>make -r world: build failed. Please re-run make with -j1 V=s to see
>what's going on
>/home/vagrant/firmware/build/ar71xx/include/toplevel.mk:198: recipe for
>target 'world' failed
>make: *** [world] Error 1
>cp: cannot stat
>'./build/ar71xx/bin/targets/ar71xx/generic/lede-ar71xx-generic-cpe210-220-squashfs-sysupgrade.bin':
>No such file or directory
>cp: cannot stat
>'./build/ar71xx/bin/targets/ar71xx/generic/lede-ar71xx-generic-cpe510-520-squashfs-sysupgrade.bin':
>No such file or directory
>cp: cannot stat
>'./build/ar71xx/bin/targets/ar71xx/generic/lede-ar71xx-generic-ubnt-nano-m-squashfs-sysupgrade.bin':
>No such file or directory
>cp: cannot stat
>'./build/ar71xx/bin/targets/ar71xx/generic/lede-ar71xx-generic-ubnt-loco-m-xw-squashfs-sysupgrade.bin':
>No such file or directory
>cp: cannot stat
>'./build/ar71xx/bin/targets/ar71xx/generic/lede-ar71xx-generic-tl-wr740n-v4-squashfs-sysupgrade.bin':
>No such file or directory
>cp: cannot stat
>'./build/ar71xx/bin/targets/ar71xx/generic/lede-ar71xx-generic-tl-wr741nd-v2-squashfs-sysupgrade.bin':
>No such file or directory
>cp: cannot stat
>'./build/ar71xx/bin/targets/ar71xx/generic/lede-ar71xx-generic-tl-wr741nd-v4-squashfs-sysupgrade.bin':
>No such file or directory
>cp: cannot stat
>'./build/ar71xx/bin/targets/ar71xx/generic/lede-ar71xx-generic-tl-wr841-v7-squashfs-sysupgrade.bin':
>No such file or directory
>cp: cannot stat
>'./build/ar71xx/bin/targets/ar71xx/generic/lede-ar71xx-generic-tl-wr841-v8-squashfs-sysupgrade.bin':
>No such file or directory
>cp: cannot stat
>'./build/ar71xx/bin/targets/ar71xx/generic/lede-ar71xx-generic-tl-wr841-v9-squashfs-sysupgrade.bin':
>No such file or directory
>cp: cannot stat
>'./build/ar71xx/bin/targets/ar71xx/generic/lede-ar71xx-generic-tl-wr841-v10-squashfs-sysupgrade.bin':
>No such file or directory
>cp: cannot stat
>'./build/ar71xx/bin/targets/ar71xx/generic/lede-ar71xx-generic-tl-wr841-v11-squashfs-sysupgrade.bin':
>No such file or directory
>cp: cannot stat
>'./build/ar71xx/bin/targets/ar71xx/generic/lede-ar71xx-generic-tl-wr841-v12-squashfs-sysupgrade.bin':
>No such file or directory
>cp: cannot stat
>'./build/ar71xx/bin/targets/ar71xx/generic/lede-ar71xx-generic-tl-wr842n-v2-squashfs-sysupgrade.bin':
>No such file or directory
>cp: cannot stat
>'./build/ar71xx/bin/targets/ar71xx/generic/lede-ar71xx-generic-tl-wr1043nd-v1-squashfs-sysupgrade.bin':
>No such file or directory
>cp: cannot stat
>'./build/ar71xx/bin/targets/ar71xx/generic/lede-ar71xx-generic-tl-wr1043nd-v2-squashfs-sysupgrade.bin':
>No such file or directory
>cp: cannot stat
>'./build/ar71xx/bin/targets/ar71xx/generic/lede-ar71xx-generic-tl-wr1043nd-v3-squashfs-sysupgrade.bin':
>No such file or directory
>cp: cannot stat
>'./build/ar71xx/bin/targets/ar71xx/generic/lede-ar71xx-generic-tl-wr1043nd-v4-squashfs-sysupgrade.bin':
>No such file or directory
>cp: cannot stat
>'./build/ar71xx/bin/targets/ar71xx/generic/lede-ar71xx-generic-tl-wr1043n-v5-squashfs-sysupgrade.bin':
>No such file or directory
>cp: cannot stat
>'./build/ar71xx/bin/targets/ar71xx/generic/lede-ar71xx-generic-tl-wa860re-v1-squashfs-sysupgrade.bin':
>No such file or directory
>cp: cannot stat
>'./build/ar71xx/bin/targets/ar71xx/generic/lede-ar71xx-generic-tl-wa850re-v1-squashfs-sysupgrade.bin':
>No such file or directory
>cp: cannot stat
>'./build/ar71xx/bin/targets/ar71xx/generic/lede-ar71xx-generic-tl-wa901nd-v2-squashfs-sysupgrade.bin':
>No such file or directory
>cp: cannot stat
>'./build/ar71xx/bin/targets/ar71xx/generic/lede-ar71xx-generic-gl-ar150-squashfs-sysupgrade.bin':
>No such file or directory
>cp: cannot stat
>'./build/ar71xx/bin/targets/ar71xx/generic/lede-ar71xx-generic-tl-mr3020-v1-squashfs-sysupgrade.bin':
>No such file or directory
>cp: cannot stat
>'./build/ar71xx/bin/targets/ar71xx/generic/lede-ar71xx-generic-ubnt-bullet-m-squashfs-sysupgrade.bin':
>No such file or directory
>cp: cannot stat
>'./build/ar71xx/bin/targets/ar71xx/generic/lede-ar71xx-generic-ubnt-unifi-squashfs-sysupgrade.bin':
>No such file or directory
>cp: cannot stat
>'./build/ar71xx/bin/targets/ar71xx/generic/lede-ar71xx-generic-ubnt-unifiac-lite-squashfs-sysupgrade.bin':
>No such file or directory
>cp: cannot stat
>'./build/ar71xx/bin/targets/ar71xx/generic/lede-ar71xx-generic-tl-wdr3500-v1-squashfs-sysupgrade.bin':
>No such file or directory
>cp: cannot stat
>'./build/ar71xx/bin/targets/ar71xx/generic/lede-ar71xx-generic-tl-wdr3600-v1-squashfs-sysupgrade.bin':
>No such file or directory
>cp: cannot stat
>'./build/ar71xx/bin/targets/ar71xx/generic/lede-ar71xx-generic-tl-wdr4300-v1-squashfs-sysupgrade.bin':
>No such file or directory
>cp: cannot stat
>'./build/ar71xx/bin/targets/ar71xx/generic/lede-ar71xx-generic-tl-wdr4310-v1-squashfs-sysupgrade.bin':
>No such file or directory
>cp: cannot stat
>'./build/ar71xx/bin/targets/ar71xx/generic/lede-ar71xx-generic-archer-c7-v2-squashfs-sysupgrade.bin':
>No such file or directory
>cp: cannot stat
>'./build/ar71xx/bin/targets/ar71xx/generic/lede-ar71xx-generic-archer-c25-v1-squashfs-sysupgrade.bin':
>No such file or directory
>
>Hat jemand eine Idee dazu?
>
>VG
>
>-- 
>*Steampixel*
>Inhaber: Christoph Stitz
>Erthalstraße 6
>97074 Würzburg
>
>*Kontakt*
>Mail: info at steampixel.de
>Tel: 0931 417 282 21
>Mobil: 0157 805 767 30
>Web: steampixel.de
>
>*Bürozeiten*
>Mo-Fr von 9-17 Uhr

-- 
Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.
-------------- nächster Teil --------------
Ein Dateianhang mit HTML-Daten wurde abgetrennt...
URL: <http://lists.freifunk.net/pipermail/franken-dev-freifunk.net/attachments/20180731/53a542a1/attachment.html>


Mehr Informationen über die Mailingliste franken-dev