public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Michael Ellerman <mpe@ellerman•id.au>
To: Stephen Rothwell <sfr@canb•auug.org.au>,
	Linux-Next Mailing List <linux-next@vger•kernel.org>,
	robh@kernel•org
Cc: Linux Kernel Mailing List <linux-kernel@vger•kernel.org>
Subject: Re: linux-next: Tree for Sep 20
Date: Thu, 20 Sep 2018 20:37:37 +1000	[thread overview]
Message-ID: <87d0t8jvym.fsf@concordia.ellerman.id.au> (raw)
In-Reply-To: <20180920151243.5524c6ca@canb.auug.org.au>

Stephen Rothwell <sfr@canb•auug.org.au> writes:

> Hi all,
>
> Changes since 20180919:
>
> Dropped trees: xarray, ida (temporarily)
>
> The input-current tree lost its build failure.
>
> I still disabled building some samples in the vfs tree.
>
> Non-merge commits (relative to Linus' tree): 4279
>  4792 files changed, 166265 insertions(+), 93138 deletions(-)

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?

cheers

  reply	other threads:[~2018-09-20 10:37 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-20  5:12 linux-next: Tree for Sep 20 Stephen Rothwell
2018-09-20 10:37 ` Michael Ellerman [this message]
2018-09-20 11:10   ` Stephen Rothwell
2018-09-20 11:17     ` Stephen Rothwell
2018-09-20 14:02       ` Rob Herring
2018-09-24  3:43         ` Michael Ellerman
  -- strict thread matches above, loose matches on Subject: below --
2024-09-20  4:33 Stephen Rothwell
2023-09-20  3:37 Stephen Rothwell
2022-09-20  8:15 Stephen Rothwell
2021-09-20  6:35 Stephen Rothwell
2019-09-20 16:36 Mark Brown
2017-09-20  4:21 Stephen Rothwell
2016-09-20  8:04 Stephen Rothwell
2013-09-20  4:45 Stephen Rothwell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87d0t8jvym.fsf@concordia.ellerman.id.au \
    --to=mpe@ellerman$(echo .)id.au \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=robh@kernel$(echo .)org \
    --cc=sfr@canb$(echo .)auug.org.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox