From: "Randy.Dunlap" <rddunlap@osdl.org>
To: Ian Pilcher <i.pilcher@comcast.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Checking patch for non-x86 bugs
Date: Thu, 8 Jan 2004 10:19:36 -0800 [thread overview]
Message-ID: <20040108101936.41578f55.rddunlap@osdl.org> (raw)
In-Reply-To: <3FFD17B5.90603@comcast.net>
On Thu, 08 Jan 2004 02:41:25 -0600 Ian Pilcher <i.pilcher@comcast.net> wrote:
| I know that this is probably wishful thinking, but "they" always say
| that the only stupid question is the one you don't ask. (Whoever "they"
| are, they are decidedly wrong about this, BTW.)
|
| I have a patch that adds an x86-specific sysctl. I believe that every-
| thing is properly #ifdef'ed, but it would be awful nice to be able to
| ensure that I haven't broken building on non-x86 architectures. Is
| there any way to do this without building a full-fledged cross-compiler
| toolchain? (And if not, does anyone know of a good HOWTO on setting up
| such a toolchain?)
You can look at http://www.kegel.com/crosstool/
to see if it can help you.
I'll look at your (previously posted) patch also.
--
~Randy
prev parent reply other threads:[~2004-01-08 18:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-08 8:41 Ian Pilcher
2004-01-08 18:19 ` Randy.Dunlap [this message]
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=20040108101936.41578f55.rddunlap@osdl.org \
--to=rddunlap@osdl.org \
--cc=i.pilcher@comcast.net \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome