linux-kernel - Re: vdso_standalone_test_x86.c build failure on Linus' tree

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] [day] [month] [year] [list]

Message-ID: <5435D449.5030403@infradead.org>
Date:	Wed, 08 Oct 2014 17:18:17 -0700
From:	Randy Dunlap <rdunlap@...radead.org>
To:	Andy Lutomirski <luto@...capital.net>,
	Peter Foley <pefoley2@...oley.com>
CC:	"H. Peter Anvin" <hpa@...or.com>,
	Chuck Ebbert <cebbert.lkml@...il.com>,
	Josh Boyer <jwboyer@...oraproject.org>,
	Jiri Kosina <jkosina@...e.cz>,
	"Linux-Kernel@...r. Kernel. Org" <linux-kernel@...r.kernel.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: vdso_standalone_test_x86.c build failure on Linus' tree

On 10/08/14 16:18, Andy Lutomirski wrote:
> On Wed, Oct 8, 2014 at 4:11 PM, Peter Foley <pefoley2@...oley.com> wrote:
>> On Wed, Oct 8, 2014 at 5:21 PM, H. Peter Anvin <hpa@...or.com> wrote:
>>> That we can't solve, but it is not okay to break the kernel build.
>>
>> Should I just make CONFIG_BUILD_DOCSRC depend on CROSS_COMPILE=""?
>> I'm not sure how much value would be added by implementing targetprogs
>> in kbuild, simply to increase build testing of Documentation/
> 
> Yes, IMO.  Let the kselftest people solve it, because they might have
> extra requirements.
> 
> --Andy

As I have said in the past, there are probably lots of source files in
Documentation/ that should be in tools/ or tools/testing/ instead.


-- 
~Randy
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/