From: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
To: David Miller <davem@davemloft.net>,
jbaron@redhat.com, linux-kernel@vger.kernel.org, mingo@elte.hu,
hpa@zytor.com, tglx@linutronix.de, rostedt@goodmis.org,
andi@firstfloor.org, roland@redhat.com, rth@redhat.com,
mhiramat@redhat.com, fweisbec@gmail.com, avi@redhat.com,
vgoyal@redhat.com, dank@kegel.com
Subject: Re: [PATCH 00/11] jump label v7
Date: Tue, 27 Apr 2010 21:49:41 -0400 [thread overview]
Message-ID: <20100428014941.GA8389@Krystal> (raw)
In-Reply-To: <20100428013951.GM12389@ozlabs.org>
* Tony Breeds (tony@bakeyournoodle.com) wrote:
> On Tue, Apr 27, 2010 at 05:58:58PM -0700, David Miller wrote:
>
> > The kernel stops compiling after the second patch because
> > kernel/jump_label.c is compiled unconditionally, and this generates an
> > attempt to include asm/alternatives.h which is an x86-only phenomenon.
> >
> > Do you have access to a cross-compile environment or at least some
> > non-x86 system you can test build on before submitting these patch
> > sets?
>
> I heard cross-compilers?
>
> http://kernel.org/pub/tools/crosstool/files/bin/ i686 and x86_64 and 4.4.0
> compilers suitable for kernel work.
>
> I plan to build 4.4.$latest and 4.5.0 ASAP.
>
> Yours Tony
The crosstool package from Dan Kegel did a good job for this. Not sure
it's currently maintained though. It was a very useful project, it's a
shame if it does not live on. It would be good to have up-to-date and
tested compilers for various architectures available on kernel.org,
ideally with access to a package that helps building compilers for
various architectures.
Thanks,
Mathieu
--
Mathieu Desnoyers
Operating System Efficiency R&D Consultant
EfficiOS Inc.
http://www.efficios.com
next prev parent reply other threads:[~2010-04-28 1:50 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-16 15:24 [PATCH 00/11] jump label v7 Jason Baron
2010-04-16 15:24 ` [PATCH 01/11] jump label: notifier atomic call chain notrace Jason Baron
2010-04-16 15:24 ` [PATCH 02/11] jump label: base patch Jason Baron
2010-04-16 15:24 ` [PATCH 03/11] jump label: x86 support Jason Baron
2010-04-16 15:24 ` [PATCH 04/11] jump label: tracepoint support Jason Baron
2010-04-16 15:24 ` [PATCH 05/11] jump label: add module support Jason Baron
2010-04-16 15:24 ` [PATCH 06/11] jump label: move ftrace_dyn_arch_init to common code Jason Baron
2010-04-16 15:24 ` [PATCH 07/11] jump label: sort jump table at build-time Jason Baron
2010-04-16 15:24 ` [PATCH 08/11] jump label: initialize workqueue tracepoints *before* they are registered Jason Baron
2010-04-16 15:24 ` [PATCH 09/11] jump label: jump_label_text_reserved() to reserve our jump points Jason Baron
2010-04-16 15:24 ` [PATCH 10/11] sparc64: Add jump_label support Jason Baron
2010-04-16 15:25 ` [PATCH 11/11] jump label: add docs Jason Baron
2010-04-22 23:17 ` [PATCH 00/11] jump label v7 David Miller
2010-04-28 0:58 ` David Miller
2010-04-28 1:39 ` Tony Breeds
2010-04-28 1:49 ` Mathieu Desnoyers [this message]
2010-04-28 2:08 ` Tony Breeds
2010-04-28 2:13 ` Mike Frysinger
2010-04-28 14:09 ` Mathieu Desnoyers
2010-04-28 21:53 ` H. Peter Anvin
2010-04-29 18:15 ` Jason Baron
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=20100428014941.GA8389@Krystal \
--to=mathieu.desnoyers@polymtl.ca \
--cc=andi@firstfloor.org \
--cc=avi@redhat.com \
--cc=dank@kegel.com \
--cc=davem@davemloft.net \
--cc=fweisbec@gmail.com \
--cc=hpa@zytor.com \
--cc=jbaron@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@redhat.com \
--cc=mingo@elte.hu \
--cc=roland@redhat.com \
--cc=rostedt@goodmis.org \
--cc=rth@redhat.com \
--cc=tglx@linutronix.de \
--cc=vgoyal@redhat.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