From: Vincenzo Frascino <vincenzo.frascino@arm.com>
To: Matteo Croce <mcroce@redhat.com>
Cc: Will Deacon <will@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: build error
Date: Mon, 29 Jul 2019 12:08:50 +0100 [thread overview]
Message-ID: <cc6f9c8f-a4a1-7c71-1f89-72e1e8dd0cc8@arm.com> (raw)
In-Reply-To: <CAGnkfhxXHPfMZVMy4Wjmy39E3Oh2U8FjVU8p8PprCnj5QFLMEg@mail.gmail.com>
Hi Matteo,
On 29/07/2019 11:25, Matteo Croce wrote:
> On Mon, Jul 29, 2019 at 12:16 PM Vincenzo Frascino
> <vincenzo.frascino@arm.com> wrote:
>>
>> Hi Matteo and Will,
>>
>>
>> If I try to build a fresh kernel on my machine with the standard "make mrproper
>> && make defconfig && make" I do not see the reported issue (Please see below
>> scissors).
>>
>> At this point would be interesting to know more about how Matteo is building the
>> kernel, and try to reproduce the issue here.
>>
>> @Matteo, could you please provide the full .config and the steps you used to
>> generate it? Is it an 'oldconfig'?
>>
>
> Hi,
>
> yes, this is an oldconfig from a vanilla 5.2, I attach it
> (the non gzipped config was dropped by the ML filter)
>
>
I tried your config file and seems working correctly:
# cp ~/config ../linux-out/.config
# make oldconfig
# make
arch/arm64/Makefile:56: CROSS_COMPILE_COMPAT not defined or empty, the compat
vDSO will not be built
---
Could you please send to me the config file that does not contain:
CONFIG_CROSS_COMPILE_COMPAT_VDSO=""
The original one I mean, on which you did not run make oldconfig.
My suspect at this point is that the string passed to
CONFIG_CROSS_COMPILE_COMPAT_VDSO is not completely empty.
In fact if I do CONFIG_CROSS_COMPILE_COMPAT_VDSO=" " (single space),
I do have a failure similar to the one you reported.
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
>
--
Regards,
Vincenzo
next prev parent reply other threads:[~2019-07-29 11:08 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
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 [this message]
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=cc6f9c8f-a4a1-7c71-1f89-72e1e8dd0cc8@arm.com \
--to=vincenzo.frascino@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mcroce@redhat.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).