From: Randolph Chung <randolph@tausq.org>
To: Markus Grabert <xam@student.cs.ucc.ie>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] State of official Linux kernel
Date: Mon, 19 Nov 2001 12:03:56 -0800 [thread overview]
Message-ID: <20011119120355.Q3053@tausq.org> (raw)
In-Reply-To: <Pine.OSF.4.41.0111191911120.11606-100000@student.cs.ucc.ie>
> I'm just curious what the state of the PA-RISC support of the
> official linux kernel is (2.4.14 from kernel.org).
2.4.14 kernel images are now available from the Debian archive. It is
also available from parisc-linux cvs.
I'm not sure what's the status of merging into the main tree though.
> What about gcc, gdb, glibc and binutils ? How long do you think does it
> take to get the current fixes/patches into a release ?
We work with folks that are "upstream" for these tools to incorporate
parisc specific changes into the mainline sources. Other than gdb I
believe we have very little debian/parisc specific patches.
> AFAIK RedHat/Cygnus supports/maintains gcc, gdb, glibc and binutils.
> Are there (usually) any problems to get the patches/fixes (of gcc, gdb,
> ...) into a official release ? How good is the cooperation with the main
> developers of these tools/libraries ? RedHat doesn't seem to be interested
> in an Linux/PA-RISC port and debian is something like a competitor ...
Without guessing about any political issues, I'd say that upstream has
been very cooperative in general in accepting parisc-linux port changes.
I'm not sure why you think this is/will be otherwise.
randolph
--
@..@ http://www.TauSq.org/
(----)
( >__< )
^^ ~~ ^^
next prev parent reply other threads:[~2001-11-19 20:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-19 19:40 [parisc-linux] State of official Linux kernel Markus Grabert
2001-11-19 20:03 ` Randolph Chung [this message]
2001-11-19 20:13 ` Jurriaan on Alpha
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=20011119120355.Q3053@tausq.org \
--to=randolph@tausq.org \
--cc=parisc-linux@lists.parisc-linux.org \
--cc=xam@student.cs.ucc.ie \
/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