From: Rob Herring <robh@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Michael Ellerman <mpe@ellerman.id.au>,
linux-next <linux-next@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for Sep 20
Date: Thu, 20 Sep 2018 07:02:30 -0700 [thread overview]
Message-ID: <CAL_JsqLRRCdOWABiTYHp7jupdiLfPRv95OSKWVB-HX=cevdQMg@mail.gmail.com> (raw)
In-Reply-To: <20180920211755.1fabd744@canb.auug.org.au>
On Thu, Sep 20, 2018 at 4:18 AM Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> 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."
Looks like until a recent commit, this also included nconfig and
menuconfig, but those were dropped after some complaints. I'll rework
this to make things work with pkg-config.
Rob
next prev parent reply other threads:[~2018-09-20 14:02 UTC|newest]
Thread overview: 15+ 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
2018-09-20 14:02 ` Rob Herring [this message]
2018-09-24 3:43 ` Michael Ellerman
2018-09-24 3:43 ` Michael Ellerman
-- strict thread matches above, loose matches on Subject: below --
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
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='CAL_JsqLRRCdOWABiTYHp7jupdiLfPRv95OSKWVB-HX=cevdQMg@mail.gmail.com' \
--to=robh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mpe@ellerman.id.au \
--cc=sfr@canb.auug.org.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.