| 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
| ||
|
Message-ID: <CALCETrU=OZBbQhzi-7mSM5AXor15rqynrVippv9nMbKCxHGu7A@mail.gmail.com> Date: Mon, 22 Jun 2015 10:01:36 -0700 From: Andy Lutomirski <luto@...capital.net> To: Jonathan Corbet <corbet@....net> Cc: Paul Gortmaker <paul.gortmaker@...driver.com>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "linux-doc@...r.kernel.org" <linux-doc@...r.kernel.org> Subject: Re: [PATCH] Documentation/vDSO: don't build tests when cross compiling On Mon, Jun 22, 2015 at 9:41 AM, Jonathan Corbet <corbet@....net> wrote: > 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? Agreed. What gcc version is this? --Andy > > Thanks, > > jon -- Andy Lutomirski AMA Capital Management, LLC -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists