Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <dan@debian.org>
To: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
Cc: "H . J . Lu" <hjl@lucon.org>, linux-mips@oss.sgi.com
Subject: Re: New toolchain for Linux/mips
Date: Wed, 6 Jun 2001 11:00:19 -0700	[thread overview]
Message-ID: <20010606110019.A23009@nevyn.them.org> (raw)
In-Reply-To: <Pine.GSO.3.96.1010606193612.2113E-100000@delta.ds2.pg.gda.pl>; from macro@ds2.pg.gda.pl on Wed, Jun 06, 2001 at 07:48:24PM +0200

On Wed, Jun 06, 2001 at 07:48:24PM +0200, Maciej W. Rozycki wrote:
> On Wed, 6 Jun 2001, H . J . Lu wrote:
> 
> > There are many changes in gdb, especially in thread and C++ supports.
> > We need those on mips also. I am willing to spend my time. But I need
> > some help. I don't know much about mips :-(.
> 
>  It would be nice to have at least basic C support in mainline. 
> 
> > I'd like to get gdb working first. Do you have time to answer some
> > questions?
> 
>  I often have time to write mails (but I don't have most of my development
> resources here).  Feel free to ask -- I'll try to answer as I can.  I
> haven't been into MIPS/Linux development tools for some time now, since
> they are mostly working for me, so my memory might be vague.  I'm working
> on the kernel mostly these days -- my primary goal is to find out why
> Linux crashes hard when building binutils natively on my DECstation (the
> progress is at a snail speed, unfortunately). 

I've actually spent this week porting the gdb CVS head to MIPS; I've
got it almost entirely working now.  There's one problem with SIGTRAP
that I haven't quite figured out yet, and thread attach isn't quite
working, and there's a kernel bug I've been repeatedly triggering that
I think I just fixed.  I anticipate it all being done in a couple of
days - I'll post here and on the GDB list when I have it in slightly
better shape.

-- 
Daniel Jacobowitz                           Debian GNU/Linux Developer
Monta Vista Software                              Debian Security Team

  reply	other threads:[~2001-06-06 18:28 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-06  5:06 New toolchain for Linux/mips H . J . Lu
2001-06-06  6:22 ` Ralf Baechle
2001-06-06  7:29   ` Geert Uytterhoeven
2001-06-06 10:44 ` Maciej W. Rozycki
2001-06-06 14:15   ` H . J . Lu
2001-06-06 15:47     ` Maciej W. Rozycki
2001-06-06 16:08       ` H . J . Lu
2001-06-06 17:48         ` Maciej W. Rozycki
2001-06-06 18:00           ` Daniel Jacobowitz [this message]
2001-06-06 18:40             ` Maciej W. Rozycki
2001-06-06 20:24               ` Daniel Jacobowitz
2001-06-06 21:09                 ` Ralf Baechle
2001-06-07 10:37                 ` Maciej W. Rozycki
2001-06-07 19:17                   ` Daniel Jacobowitz
2001-06-07 19:35                     ` Maciej W. Rozycki
2001-06-07 19:41                       ` Daniel Jacobowitz
2001-06-06 20:19           ` H . J . Lu
2001-06-07 10:32             ` Maciej W. Rozycki
2001-06-07 16:28               ` H . J . Lu
2001-06-07 17:03                 ` Maciej W. Rozycki

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=20010606110019.A23009@nevyn.them.org \
    --to=dan@debian.org \
    --cc=hjl@lucon.org \
    --cc=linux-mips@oss.sgi.com \
    --cc=macro@ds2.pg.gda.pl \
    /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