From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Michael Ellerman <mpe@ellerman.id.au>, robh@kernel.org
Cc: Linux-Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for Sep 20
Date: Thu, 20 Sep 2018 21:17:55 +1000 [thread overview]
Message-ID: <20180920211755.1fabd744@canb.auug.org.au> (raw)
In-Reply-To: <20180920210711.4561abee@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 1260 bytes --]
Hi Michael,
On Thu, 20 Sep 2018 21:10:08 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> 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
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> 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
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2018-09-20 11:17 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
2018-09-20 11:10 ` Stephen Rothwell
2018-09-20 11:17 ` Stephen Rothwell [this message]
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=20180920211755.1fabd744@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mpe@ellerman.id.au \
--cc=robh@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).