lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <cc6f9c8f-a4a1-7c71-1f89-72e1e8dd0cc8@arm.com>
Date:   Mon, 29 Jul 2019 12:08:50 +0100
From:   Vincenzo Frascino <vincenzo.frascino@....com>
To:     Matteo Croce <mcroce@...hat.com>
Cc:     Will Deacon <will@...nel.org>, LKML <linux-kernel@...r.kernel.org>,
        Linux ARM <linux-arm-kernel@...ts.infradead.org>
Subject: Re: build error

Hi Matteo,

On 29/07/2019 11:25, Matteo Croce wrote:
> On Mon, Jul 29, 2019 at 12:16 PM Vincenzo Frascino
> <vincenzo.frascino@....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@...ts.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
> 

-- 
Regards,
Vincenzo

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ