From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Masahiro Yamada <masahiroy@kernel.org>
Cc: Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: ARCH=arm64 build breakage for Kbuild for-next branch
Date: Wed, 3 Jun 2020 21:22:50 +1000 [thread overview]
Message-ID: <20200603212250.69feb53b@canb.auug.org.au> (raw)
In-Reply-To: <20200603142404.33123d7d@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 1248 bytes --]
Hi all,
On Wed, 3 Jun 2020 14:24:04 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> On Wed, 3 Jun 2020 13:11:59 +0900 Masahiro Yamada <masahiroy@kernel.org> wrote:
> >
> > If you pull the latest kbuild for-next branch,
> > ARCH=arm64 will fail to build.
> >
> > I will fix it soon.
> >
> > For today's linux-next, you can patch
> > as follows.
> > (or, you can use the old branch)
> >
> >
> > diff --git a/Makefile b/Makefile
> > index f80c4ff93ec9..fbb4b95ae648 100644
> > --- a/Makefile
> > +++ b/Makefile
> > @@ -1074,7 +1074,7 @@ build-dirs := $(vmlinux-dirs)
> > clean-dirs := $(vmlinux-alldirs)
> >
> > # Externally visible symbols (used by link-vmlinux.sh)
> > -KBUILD_VMLINUX_OBJS := $(head-y) $(addsuffix built-in.a, $(core-y))
> > +KBUILD_VMLINUX_OBJS := $(head-y) $(patsubst %/,%/built-in.a, $(core-y))
> > KBUILD_VMLINUX_OBJS += $(addsuffix built-in.a, $(filter %/, $(libs-y)))
> > ifdef CONFIG_MODULES
> > KBUILD_VMLINUX_OBJS += $(patsubst %/, %/lib.a, $(filter %/, $(libs-y)))
>
> OK, thanks, I will apply that at some point, since I have already
> merged your tree.
And then I forgot, sorry. I assume it will be fixed tomorrow.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2020-06-03 11:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-03 4:11 Masahiro Yamada
2020-06-03 4:24 ` Stephen Rothwell
2020-06-03 11:22 ` Stephen Rothwell [this message]
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=20200603212250.69feb53b@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@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
all inboxes | Powered by JetHome®