linux-kernel - Re: [PATCH] Documentation/vDSO: don't build tests when cross compiling

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]

Date:	Mon, 22 Jun 2015 10:41:24 -0600
From:	Jonathan Corbet <corbet@....net>
To:	Paul Gortmaker <paul.gortmaker@...driver.com>
Cc:	<linux-kernel@...r.kernel.org>, <linux-doc@...r.kernel.org>,
	Andy Lutomirski <luto@...capital.net>
Subject: Re: [PATCH] Documentation/vDSO: don't build tests when cross
 compiling

On Sat, 20 Jun 2015 21:10:28 -0400
Paul Gortmaker <paul.gortmaker@...driver.com> wrote:

> The following was seen in linux-next build coverage, which is somewhat
> unique since it uses powerpc host to cross compile x86:
> 
> Documentation/vDSO/vdso_standalone_test_x86.c:49:2: error: impossible
> register constraint in 'asm'
> make[4]: *** [Documentation/vDSO/vdso_standalone_test_x86.o] Error 1
> 
> It probably makes sense to just skip building these tests when
> we are cross compiling.

So I guess I'm not totally averse to applying these; getting rid of build
errors is a good thing.  But I do get the feeling like it's papering over
the real problem.  As a general rule, cross-compiling works; what's
special about these programs that makes it fail?

Thanks,

jon
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
Please read the FAQ at  http://www.tux.org/lkml/