2004-01-08 08:41:29

by Ian Pilcher

[permalink] [raw]
Subject: Checking patch for non-x86 bugs

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?)

Thanks!
--
========================================================================
Ian Pilcher [email protected]
========================================================================


2004-01-08 18:26:18

by Randy.Dunlap

[permalink] [raw]
Subject: Re: Checking patch for non-x86 bugs

On Thu, 08 Jan 2004 02:41:25 -0600 Ian Pilcher <[email protected]> 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