Dependencies missing

[drtyhlpr]

Dependencies missing

[gfa]

i had to install device-tree-compiler to be able to build the kernel (rpi 3)

[drtyhlpr]

thanks for the info will patch soon. sorry for the delay

[drtyhlpr]

hm I tested it today. Running Debian jessie from netinstall with only "essential system tools" installed inside vmware.

jessie:
psmisc: should be a jessie default package
build-essential: should not be required
bc -> added with patch
dbus: should be a jessie default package

the "crossbuild-essential-armhf" was removed from jessie and emdedian repo has to be added:

echo "deb http://emdebian.org/tools/debian/ jessie main" > /etc/apt/sources.list.d/crosstools.list
sudo -u nobody wget -O - http://emdebian.org/tools/debian/emdebian-toolchain-archive.key | apt-key add -
dpkg --add-architecture armhf
apt-get update

(updating readme soon)

ps.
stretch:
bc -> just added with patch
psmisc -> just added with patch
rest seems to work out of the box. testing running releases soon rpi2 - rpi3

[drtyhlpr]

@gfa hi, can you tell me what command lines you used for device tree compilation. are the default ones included in the rpi2/3 kernel sources not working (any more)? or did you have a problem with a specific dev driver?

[gfa]

@drtyhlpr

using today's code

  LD      drivers/usb/phy/built-in.o
  LD      drivers/usb/ulpi/built-in.o
  DTC     arch/arm/dts/bcm2835-rpi-a-plus.dtb
/bin/sh: 1: dtc: not found
scripts/Makefile.lib:322: recipe for target 'arch/arm/dts/bcm2835-rpi-a-plus.dtb' failed
make[3]: *** [arch/arm/dts/bcm2835-rpi-a-plus.dtb] Error 127
dts/Makefile:36: recipe for target 'arch-dtbs' failed
make[2]: *** [arch-dtbs] Error 2
Makefile:1217: recipe for target 'dts' failed
make[1]: *** [dts] Error 2
Makefile:460: recipe for target '__build_one_by_one' failed
make: *** [__build_one_by_one] Error 2
make: Leaving directory '/tmp/u-boot'
+ cleanup

and my command line is

ENABLE_UBOOT=true ENABLE_CONSOLE=false ENABLE_IPV6=true  ENABLE_HARDNET=false ENABLE_IPTABLES=false APT_SERVER=deb.debian.org  ENABLE_MINBASE=true ENABLE_MINGPU=true EXPANDROOT
=false RELEASE=stretch RPI_MODEL=3  ENABLE_WIRELESS=true  PASSWORD="root" EXPANDROOT=false ENABLE_SOUND=false ENABLE_HWRANDOM=false ENABLE_UBOOT=true ENABLE_USER=false REDUCE_DOC=true REDUCE_MAN=true  ./rpi23-gen-image.sh

note, i'm not using jessie on the build host but stretch

[drtyhlpr]

ah you are using UBOOT. well I tried it some months ago and failed to get the device up and running with it. (dark/lsdcolor screen on all configuration tries) -> #47.

so with using "apt-get install device-tree-compiler" (or adding it to the APT required packages) it was/is working? sorry I don't have any rpi around and will be able to test next weekend.

ps. with "working" i mean - uboot is compiling and the system is booting after it was installed

[gfa]

Later down the road I found #47, I removed uboot from the options and installed device-tree-compiler and the image worked fine 😀 Do you want me to test without uboot if the problem appears again? I didn't test without uboot and without device-tree-compiler I don't have a pi to test but I can test the image creation

…

On January 6, 2017 7:32:01 PM GMT+08:00, drtyhlpr ***@***.***> wrote: ah you are using UBOOT. well I tried it some months ago and failed to get the device up and running with it. (dark/lsdcolor screen on all configuration tries) -> #47. so with using "apt-get install device-tree-compiler" (or adding it to the APT required packages) it was/is working? sorry I don't have any rpi around and will be able to test next weekend. -- You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub: #59 (comment)

-- Sent from my Android device with K-9 Mail. Please excuse my brevity.

[drtyhlpr]

hehe same here... of course all tests and results from your side would be nice. but I think I am just doing exatly the same on some slower vmware hosts. (building on jessie and stretch - added device-tree-compiler etc.).. hitting the console every 30min and doing other so called work in between :)

what currently worries me the most is: #61 - I had this problems before as described and invested alot of time to debug and stuff ... without success. problem automatically solved 1-2 weeks later... maybe I got a RPi3 available next to me on Sunday .

[drtyhlpr]

seems fixed. testing with various parameter combinations the next days