Hi Michael,

On Thu, 20 Sep 2018 20:37:37 +1000 Michael Ellerman <mpe@ellerman.id.au> wrote:
>
> Oodles of:
> 
>   # < make -s -j 48 ARCH=arm64 O=/kisskb/build/linux-next_arm64-allnoconfig_arm64 CROSS_COMPILE=/opt/cross/kisskb/br-aarch64-glibc-2016.08-613-ge98b4dd/bin/aarch64-linux-  allnoconfig
>   # make -s -j 48 ARCH=arm64 O=/kisskb/build/linux-next_arm64-allnoconfig_arm64 CROSS_COMPILE=/opt/cross/kisskb/br-aarch64-glibc-2016.08-613-ge98b4dd/bin/aarch64-linux-  
>   /bin/sh: 1: pkg-config: not found
>   make[3]: pkg-config: Command not found
>   /kisskb/src/scripts/dtc/yamltree.c:23:10: fatal error: yaml.h: No such file or directory
>    #include <yaml.h>
>             ^~~~~~~~
>   compilation terminated.
>   make[3]: *** [scripts/Makefile.host:107: scripts/dtc/yamltree.o] Error 1
>   make[3]: *** Waiting for unfinished jobs....
>   make[2]: *** [/kisskb/src/scripts/Makefile.build:536: scripts/dtc] Error 2
>   make[2]: *** Waiting for unfinished jobs....
>   make[1]: *** [/kisskb/src/Makefile:1067: scripts] Error 2
>   make: *** [Makefile:146: sub-make] Error 2
> 
> http://kisskb.ellerman.id.au/kisskb/head/a0cb0cabe4bbeacf5ed9e81a41abcbae47ba925a/
> 
> 
> I guess we've got a yaml dependency now?

Yeah, but it is tested for and worked for my builds during the day (I
don't have it installed on my build machine either ...  do we have
pkg-config installed in the build images?

Anyway, it is (presuambly) caused by commit

  52786e7517a2 ("scripts/dtc: Update to upstream version v1.4.7-14-gc86da84d30e4")

from the devicetree tree.

-- 
Cheers,
Stephen Rothwell