linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Franz Sirl <Franz.Sirl-kernel@lauterbach.com>
To: "Kevin Buettner" <kev@primenet.com>,
	"Kevin B. Hendricks" <kbhend@business.wm.edu>,
	linuxppc-dev@lists.linuxppc.org
Subject: Re: gdb broken under linuxppc r5 tools
Date: Sun, 1 Aug 1999 22:54:30 +0200	[thread overview]
Message-ID: <99080122552500.00423@ns1102.munich.netsurf.de> (raw)
In-Reply-To: <990801202455.ZM22552@redrock.lan>


Am Son, 01 Aug 1999 schrieb Kevin Buettner:
>Kevin, Franz, et.al,
>
>Earlier this year, Metrowerks and I signed the copyright assignments
>required by the FSF.  Beginning August 9, I will be starting work at
>Cygnus as a GDB engineer.  One of the things that I'll work on is a
>merge of my patches into the current gdb mainline.  It'll be my goal
>to get a solid, usable gdb up and running on Linux/PPC again.

Wow, that are really great news! Congrats!

Franz.

[[ This message was sent via the linuxppc-dev mailing list.  Replies are ]]
[[ not  forced  back  to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting.   ]]

  reply	other threads:[~1999-08-01 20:54 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-08-01 13:01 current recommended versions of glibc/egcs/binutils for R5? R Shapiro
1999-08-01 13:58 ` Franz Sirl
1999-08-01 18:38   ` gdb broken under linuxppc r5 tools Kevin B. Hendricks
1999-08-01 19:03     ` Franz Sirl
1999-08-01 20:12       ` kbhend
1999-08-01 20:24       ` Kevin Buettner
1999-08-01 20:54         ` Franz Sirl [this message]
1999-08-02 11:20         ` Gary Thomas
1999-08-02 15:21         ` kbhend
1999-08-02 15:50           ` Daniel Jacobowitz
1999-08-02 16:01         ` kbhend
1999-08-22 15:09   ` bug in glibc 2.1.2 new semaphore functions in libpthread? Kevin Hendricks
1999-08-24 21:09     ` Franz Sirl

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=99080122552500.00423@ns1102.munich.netsurf.de \
    --to=franz.sirl-kernel@lauterbach.com \
    --cc=kbhend@business.wm.edu \
    --cc=kev@primenet.com \
    --cc=linuxppc-dev@lists.linuxppc.org \
    /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;
as well as URLs for NNTP newsgroup(s).