[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180920211755.1fabd744@canb.auug.org.au>
Date: Thu, 20 Sep 2018 21:17:55 +1000
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Michael Ellerman <mpe@...erman.id.au>, robh@...nel.org
Cc: Linux-Next Mailing List <linux-next@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: linux-next: Tree for Sep 20
Hi Michael,
On Thu, 20 Sep 2018 21:10:08 +1000 Stephen Rothwell <sfr@...b.auug.org.au> wrote:
>
> On Thu, 20 Sep 2018 20:37:37 +1000 Michael Ellerman <mpe@...erman.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
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> don't have it installed on my build machine either ... do we have
> pkg-config installed in the build images?
Duh! ;-)
According to the commit message we gained a kconfig dependency on
pkg-config in 4.18. I wonder what else depends on it.
Ah:
"pkg-config
----------
The build system, as of 4.18, requires pkg-config to check for installed
kconfig tools and to determine flags settings for use in
'make {g,x}config'. Previously pkg-config was being used but not
verified or documented."
(from Documentation/process/changes.rst)
--
Cheers,
Stephen Rothwell
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists