From: Matteo Croce <mcroce@redhat.com>
To: Will Deacon <will@kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
Vincenzo Frascino <vincenzo.frascino@arm.com>
Subject: Re: build error
Date: Mon, 29 Jul 2019 12:08:33 +0200 [thread overview]
Message-ID: <CAGnkfhxWsaDpxsE5Asj1dUxXGJvQr4_oq4ZDWtbn-zsbh_jkMQ@mail.gmail.com> (raw)
In-Reply-To: <20190729095047.k45isr7etq3xkyvr@willie-the-truck>
On Mon, Jul 29, 2019 at 11:50 AM Will Deacon <will@kernel.org> wrote:
>
> Hi Matteo,
>
> On Sun, Jul 28, 2019 at 10:08:06PM +0200, Matteo Croce wrote:
> > I get this build error with 5.3-rc2"
> >
> > # make
> > arch/arm64/Makefile:58: gcc not found, check CROSS_COMPILE_COMPAT. Stop.
> >
> > I didn't bisect the tree, but I guess that this kconfig can be related
> >
> > # grep CROSS_COMPILE_COMPAT .config
> > CONFIG_CROSS_COMPILE_COMPAT_VDSO=""
> >
> > Does someone have any idea? Am I missing something?
>
> Can you try something like the below?
>
> Will
>
> --->8
>
> diff --git a/arch/arm64/Makefile b/arch/arm64/Makefile
> index bb1f1dbb34e8..d35ca0aee295 100644
> --- a/arch/arm64/Makefile
> +++ b/arch/arm64/Makefile
> @@ -52,7 +52,7 @@ ifeq ($(CONFIG_GENERIC_COMPAT_VDSO), y)
>
> ifeq ($(CONFIG_CC_IS_CLANG), y)
> $(warning CROSS_COMPILE_COMPAT is clang, the compat vDSO will not be built)
> - else ifeq ($(CROSS_COMPILE_COMPAT),)
> + else ifeq ("$(CROSS_COMPILE_COMPAT)","")
> $(warning CROSS_COMPILE_COMPAT not defined or empty, the compat vDSO will not be built)
> else ifeq ($(shell which $(CROSS_COMPILE_COMPAT)gcc 2> /dev/null),)
> $(error $(CROSS_COMPILE_COMPAT)gcc not found, check CROSS_COMPILE_COMPAT)
Hi, it doesn't fix. I've tried to print CROSS_COMPILE_COMPAT and it
seemed empty, but hexdump shows that it contains a new line:
# make 2>&1 |hexdump -C
00000000 61 72 63 68 2f 61 72 6d 36 34 2f 4d 61 6b 65 66 |arch/arm64/Makef|
00000010 69 6c 65 3a 35 39 3a 20 2a 2a 2a 20 43 52 4f 53 |ile:59: *** CROS|
00000020 53 5f 43 4f 4d 50 49 4c 45 5f 43 4f 4d 50 41 54 |S_COMPILE_COMPAT|
00000030 3d 27 13 27 2e 20 20 53 74 6f 70 2e 0a |='.'. Stop..|
0000003d
--
Matteo Croce
per aspera ad upstream
next prev parent reply other threads:[~2019-07-29 10:09 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-28 20:08 build error Matteo Croce
2019-07-28 20:15 ` Bernd Petrovitsch
2019-07-28 20:28 ` Matteo Croce
2019-07-29 4:44 ` Bhaskar Chowdhury
2019-07-29 7:58 ` Matteo Croce
2019-07-29 9:50 ` Will Deacon
2019-07-29 10:08 ` Matteo Croce [this message]
2019-07-29 10:16 ` Vincenzo Frascino
2019-07-29 10:21 ` Matteo Croce
2019-07-29 10:25 ` Matteo Croce
2019-07-29 11:08 ` Vincenzo Frascino
2019-07-29 11:12 ` Matteo Croce
2019-07-29 11:18 ` Vincenzo Frascino
2019-07-29 11:26 ` Matteo Croce
2019-07-29 12:54 ` [PATCH] arm64: vdso: Fix Makefile regression Vincenzo Frascino
2019-07-29 16:33 ` Matteo Croce
2019-07-31 16:23 ` Will Deacon
2019-07-31 17:09 ` Catalin Marinas
-- strict thread matches above, loose matches on Subject: below --
2010-05-28 2:54 build error ranjith kumar
2010-05-28 4:20 ` Américo Wang
2007-10-02 20:12 linux-kernel
2007-10-03 0:19 ` Stephen Hemminger
2007-10-03 0:28 ` Randy Dunlap
2007-10-03 0:39 ` Stephen Hemminger
2007-10-10 10:23 ` Wilfried Klaebe
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=CAGnkfhxWsaDpxsE5Asj1dUxXGJvQr4_oq4ZDWtbn-zsbh_jkMQ@mail.gmail.com \
--to=mcroce@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vincenzo.frascino@arm.com \
--cc=will@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).