From: Randolph Chung <tausq@debian.org>
To: James Mcclain <jmccla3@gl.umbc.edu>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] gcc-3.2 for parisc
Date: Wed, 17 Apr 2002 20:48:07 -0700 [thread overview]
Message-ID: <20020418034807.GA7563@tausq.org> (raw)
In-Reply-To: <Pine.GSO.4.31L.02.0204171535110.2863-100000@solaris1.gl.umbc.edu>
> i've seen a bit of discussion lately about people using the gcc 3.2
> snapshot on parisc linux. i would like to know if anyone has provided or
> will provide a guide to getting it going on parisc linux at all?
i plan to build unofficial debian packages of these tools in the near
future.
randolph
next prev parent reply other threads:[~2002-04-18 3:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-17 9:02 [parisc-linux] linux-2.4.18-pa19 fpu problem joel.soete
2002-04-17 11:32 ` Matthew Wilcox
2002-04-17 14:42 ` Paul Bame
2002-04-17 15:44 ` Matthew Wilcox
2002-04-17 17:24 ` joel.soete
2002-04-17 19:41 ` [parisc-linux] gcc-3.2 for parisc James Mcclain
2002-04-18 1:59 ` John David Anglin
2002-04-18 3:48 ` Randolph Chung [this message]
2002-04-21 12:43 ` [parisc-linux] linux-2.4.18-pa19 fpu problem Joel Soete
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=20020418034807.GA7563@tausq.org \
--to=tausq@debian.org \
--cc=jmccla3@gl.umbc.edu \
--cc=parisc-linux@lists.parisc-linux.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