From: Daniel Jacobowitz <dan@debian.org>
To: Ben Elliston <bje@redhat.com>
Cc: "H . J . Lu" <hjl@lucon.org>, Ralf Baechle <ralf@oss.sgi.com>,
linux-mips@oss.sgi.com
Subject: Re: PATCH: Handle Linux/mips (Re: Why is byteorder removed from /proc/cpuinfo?)
Date: Mon, 10 Dec 2001 09:21:04 -0500 [thread overview]
Message-ID: <20011210092104.A29953@nevyn.them.org> (raw)
In-Reply-To: <15380.33671.382927.402138@scooby.brisbane.redhat.com>
On Mon, Dec 10, 2001 at 08:42:31PM +1100, Ben Elliston wrote:
> >>>>> "Ben" == Ben Elliston <bje@redhat.com> writes:
>
> Ben> cpu=`cpp << EOF | grep ^mips
>
> Of course, this needs some refinement. ;-) Perhaps we need to run
> through $(CC_FOR_BUILD) -E or somesuch; cpp is no good, as it won't
> know all of the magic '*MIPS*' #defines.
HJ's patch didn't compile anything; it ran code through
$(CC_FOR_BUILD) -E :)
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2001-12-10 15:21 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-06 17:35 Why is byteorder removed from /proc/cpuinfo? H . J . Lu
2001-12-06 17:53 ` H . J . Lu
2001-12-06 17:57 ` Ralf Baechle
2001-12-06 18:36 ` PATCH: Handle Linux/mips (Re: Why is byteorder removed from /proc/cpuinfo?) H . J . Lu
2001-12-06 18:41 ` Ralf Baechle
2001-12-06 18:51 ` H . J . Lu
2001-12-06 19:16 ` Ralf Baechle
2001-12-10 7:23 ` Ben Elliston
2001-12-10 9:42 ` Ben Elliston
2001-12-10 14:21 ` Daniel Jacobowitz [this message]
2001-12-10 23:34 ` Ben Elliston
2001-12-10 23:34 ` Ben Elliston
2001-12-11 0:20 ` H . J . Lu
2001-12-11 0:23 ` Ben Elliston
2001-12-11 0:28 ` H . J . Lu
2001-12-10 18:28 ` Ralf Baechle
2001-12-10 20:24 ` Maciej W. Rozycki
2001-12-10 23:40 ` Ben Elliston
2001-12-10 23:40 ` Ben Elliston
2001-12-11 0:04 ` Maciej W. Rozycki
2001-12-11 13:30 ` Ralf Baechle
2001-12-11 23:11 ` Daniel Jacobowitz
2001-12-12 8:07 ` Ben Elliston
2001-12-10 18:40 ` Why is byteorder removed from /proc/cpuinfo? Dominic Sweetman
2001-12-10 19:06 ` Ralf Baechle
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=20011210092104.A29953@nevyn.them.org \
--to=dan@debian.org \
--cc=bje@redhat.com \
--cc=hjl@lucon.org \
--cc=linux-mips@oss.sgi.com \
--cc=ralf@oss.sgi.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 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.