| To: | Ben Elliston <bje@redhat.com> |
|---|---|
| Subject: | Re: PATCH: Handle Linux/mips (Re: Why is byteorder removed from /proc/cpuinfo?) |
| From: | Ralf Baechle <ralf@oss.sgi.com> |
| Date: | Mon, 10 Dec 2001 16:28:26 -0200 |
| Cc: | "H . J . Lu" <hjl@lucon.org>, linux-mips@oss.sgi.com |
| In-reply-to: | <15380.33671.382927.402138@scooby.brisbane.redhat.com>; from bje@redhat.com on Mon, Dec 10, 2001 at 08:42:31PM +1100 |
| References: | <20011206093506.A6496@lucon.org> <20011206155724.A11083@dea.linux-mips.net> <20011206103605.A7366@lucon.org> <15380.25324.287595.674046@scooby.brisbane.redhat.com> <15380.33671.382927.402138@scooby.brisbane.redhat.com> |
| Sender: | owner-linux-mips@oss.sgi.com |
| User-agent: | Mutt/1.2.5i |
On Mon, Dec 10, 2001 at 08:42:31PM +1100, Ben Elliston wrote: > 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. Agreed but the basic idea is good. Also this solution is suitable for crosscompilation unlike the /proc/cpuinfo thing and doesn't rely on properly installed libraries and headers might possibly of interest for building standalone software. Ralf |
| Previous by Date: | Re: the cause of spurious interrupt problem, Dominic Sweetman |
|---|---|
| Next by Date: | Re: Why is byteorder removed from /proc/cpuinfo?, Dominic Sweetman |
| Previous by Thread: | Re: PATCH: Handle Linux/mips (Re: Why is byteorder removed from /proc/cpuinfo?), H . J . Lu |
| Next by Thread: | Re: PATCH: Handle Linux/mips (Re: Why is byteorder removed from /proc/cpuinfo?), Maciej W. Rozycki |
| Indexes: | [Date] [Thread] [Top] [All Lists] |