From: Chuck Ebbert <cebbert.lkml@gmail.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Andy Lutomirski <luto@amacapital.net>,
Josh Boyer <jwboyer@fedoraproject.org>,
Peter Foley <pefoley2@pefoley.com>,
Randy Dunlap <rdunlap@infradead.org>,
Jiri Kosina <jkosina@suse.cz>,
"Linux-Kernel@Vger. Kernel. Org" <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: vdso_standalone_test_x86.c build failure on Linus' tree
Date: Wed, 8 Oct 2014 18:08:07 -0500 [thread overview]
Message-ID: <20141008180807.276dbf7c@as> (raw)
In-Reply-To: <5435AABC.2010902@zytor.com>
On Wed, 08 Oct 2014 14:21:00 -0700
"H. Peter Anvin" <hpa@zytor.com> wrote:
> On 10/08/2014 02:09 PM, Chuck Ebbert wrote:
> >>
> >> Breaking cross-compilation is not okay, though, regardless of what
> >> Fedora does. It should be okay to, for example, build an i386 kernel on
> >> an ARM box.
> >>
> >
> > I think they tried that for a while, and ended up chasing compiler
> > and makefile bugs all day. And then there's the software that wants
> > to run self-tests as part of its build...
> >
>
> That we can't solve, but it is not okay to break the kernel build.
>
Also, as Andy pointed out, when building for x86_64 we probably want
to build both 32-bit and 64-bit versions of most test programs like
this one.
next prev parent reply other threads:[~2014-10-08 23:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-08 18:52 vdso_standalone_test_x86.c build failure on Linus' tree Josh Boyer
2014-10-08 19:16 ` Andy Lutomirski
2014-10-08 19:44 ` Peter Foley
2014-10-08 20:46 ` Chuck Ebbert
2014-10-08 20:50 ` Andy Lutomirski
2014-10-08 20:55 ` H. Peter Anvin
2014-10-08 21:09 ` Chuck Ebbert
2014-10-08 21:21 ` H. Peter Anvin
2014-10-08 23:08 ` Chuck Ebbert [this message]
2014-10-08 23:11 ` Peter Foley
2014-10-08 23:18 ` Andy Lutomirski
2014-10-09 0:18 ` Randy Dunlap
2014-10-08 21:21 ` Josh Boyer
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=20141008180807.276dbf7c@as \
--to=cebbert.lkml@gmail.com \
--cc=hpa@zytor.com \
--cc=jkosina@suse.cz \
--cc=jwboyer@fedoraproject.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=pefoley2@pefoley.com \
--cc=rdunlap@infradead.org \
--cc=torvalds@linux-foundation.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.