From: Daniel Jacobowitz <dan@debian.org>
To: Toshio Seo <seo_tmi@charter.net>
Cc: Linux-Mips <linux-mips@linux-mips.org>
Subject: Re: Starter questions
Date: Tue, 3 Feb 2004 10:35:09 -0500 [thread overview]
Message-ID: <20040203153509.GA28469@nevyn.them.org> (raw)
In-Reply-To: <HGEAKBEJEJDAIDOBJGONOELECAAA.seo_tmi@charter.net>
On Tue, Feb 03, 2004 at 10:15:48AM -0500, Toshio Seo wrote:
> Hi,
>
> I am a bit new to Linux MIPS but I would really appreciate a few pointers.
>
> 1. I am getting GCC 3.3.2, binutils-2.14..... and GLIB-2.3.2 off of
> Kernel.org. Is there a source of patches for these to make a clean MIPS64
> and N32 build?
None of those three components supports N32 userspace applications.
Binutils 2.14 is pretty close. GCC 3.3.2 won't even configure for
mips64-linux.
You have to use the bleeding edge tools if you want to build a mips64
userland.
> 2. Are there any ioctl() examples for displaying and modifying processor
> registers from user programs?
>
> Thanks
> Toshio
>
>
> ---
> Outgoing mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.573 / Virus Database: 363 - Release Date: 1/28/2004
>
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
prev parent reply other threads:[~2004-02-03 15:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-03 15:15 Starter questions Toshio Seo
2004-02-03 15:35 ` Daniel Jacobowitz [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=20040203153509.GA28469@nevyn.them.org \
--to=dan@debian.org \
--cc=linux-mips@linux-mips.org \
--cc=seo_tmi@charter.net \
/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