mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Paul Gortmaker <paul.gortmaker@windriver.com>
Cc: <linux-kernel@vger.kernel.org>, <linux-doc@vger.kernel.org>,
	Andy Lutomirski <luto@amacapital.net>
Subject: Re: [PATCH] Documentation/vDSO: don't build tests when cross compiling
Date: Mon, 22 Jun 2015 10:41:24 -0600	[thread overview]
Message-ID: <20150622104124.62299220@lwn.net> (raw)
In-Reply-To: <1434849028-26733-1-git-send-email-paul.gortmaker@windriver.com>

On Sat, 20 Jun 2015 21:10:28 -0400
Paul Gortmaker <paul.gortmaker@windriver.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/

  reply	other threads:[~2015-06-22 16:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-21  1:10 Paul Gortmaker
2015-06-22 16:41 ` Jonathan Corbet [this message]
2015-06-22 17:01   ` Andy Lutomirski
2015-06-22 19:09     ` Paul Gortmaker
2015-06-22 19:46       ` Andy Lutomirski
2015-06-22 20:41         ` Paul Gortmaker
2015-06-22 21:10           ` Jonathan Corbet
2015-06-22 23:19             ` Jonathan Corbet

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=20150622104124.62299220@lwn.net \
    --to=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@amacapital.net \
    --cc=paul.gortmaker@windriver.com \
    /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
all inboxes | Powered by JetHome®