From: Randolph Chung <tausq@debian.org>
To: "M. Grabert" <xam@cs.ucc.ie>
Cc: debian-hppa@lists.debian.org, parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] Re: gcc-3.2 -> gcc-3.3 transition on hppa
Date: Sun, 2 Mar 2003 09:01:05 -0800 [thread overview]
Message-ID: <20030302170105.GU11363@tausq.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0303020911230.24978-100000@sal.ucc.ie>
> This means that future glibc (in Debian/PA-RISC, unstable) will/must
> be compiled with gcc-3.3, along with all C++-programmes. Is this going to
> happen soon or do you wait until gcc-3.3 is offically released?
this is more or less up to the Debian release manager, but we are
probably not going to start gcc-3.3 transition until the gcc-3.2
transition is over.
randolph
--
Randolph Chung
Debian GNU/Linux Developer, hppa/ia64 ports
http://www.tausq.org/
next prev parent reply other threads:[~2003-03-02 17:04 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <15968.40812.741982.606734@gargle.gargle.HOWL>
[not found] ` <15969.1828.456001.122737@gargle.gargle.HOWL>
2003-03-02 4:59 ` [parisc-linux] Re: gcc-3.2 -> gcc-3.3 transition on hppa Randolph Chung
2003-03-02 5:40 ` John David Anglin
2003-03-02 5:40 ` John David Anglin
2003-03-02 9:24 ` M. Grabert
2003-03-02 9:24 ` M. Grabert
2003-03-02 17:01 ` Randolph Chung
2003-03-02 17:01 ` Randolph Chung [this message]
2003-03-02 18:50 ` John David Anglin
2003-03-02 18:50 ` John David Anglin
2003-03-03 14:27 ` Joel Soete
2003-03-03 14:27 ` Joel Soete
2003-03-03 16:17 ` John David Anglin
2003-03-03 16:24 ` Randolph Chung
2003-03-03 17:22 ` Joel Soete
2003-03-03 16:17 ` John David Anglin
2003-03-09 20:06 ` Matthias Klose
2003-03-09 20:06 ` Matthias Klose
2003-03-09 20:27 ` John David Anglin
2003-03-09 20:45 ` Randolph Chung
2003-03-09 20:45 ` Randolph Chung
2003-03-09 20:27 ` John David Anglin
2003-03-12 17:33 ` Joel Soete
2003-03-12 17:33 ` Joel Soete
2003-03-12 17:35 ` Randolph Chung
2003-03-12 17:35 ` Randolph Chung
2003-03-12 17:53 ` Joel Soete
2003-03-12 17:53 ` Joel Soete
2003-03-14 12:48 ` Joel Soete
2003-03-14 13:17 ` Matthew Wilcox
2003-03-14 16:31 ` Joel Soete
2003-03-18 18:14 ` b.gunreben
2003-03-18 18:14 ` b.gunreben
2003-03-18 18:53 ` John David Anglin
2003-03-18 19:02 ` Randolph Chung
2003-03-18 19:16 ` John David Anglin
2003-03-18 20:21 ` Randolph Chung
2003-03-18 20:21 ` Randolph Chung
2003-03-18 20:55 ` John David Anglin
2003-03-18 20:55 ` John David Anglin
2003-03-20 17:51 ` Joel Soete
2003-03-20 17:51 ` Joel Soete
2003-03-20 18:13 ` John David Anglin
2003-03-20 18:13 ` John David Anglin
2003-03-20 18:23 ` John David Anglin
2003-03-21 12:44 ` Joel Soete
2003-03-21 13:36 ` Matthew Wilcox
2003-03-21 15:07 ` Joel Soete
2003-03-21 12:44 ` Joel Soete
2003-03-20 18:23 ` John David Anglin
2003-03-18 19:16 ` John David Anglin
2003-03-18 19:02 ` Randolph Chung
2003-03-18 21:59 ` John David Anglin
2003-03-18 21:59 ` John David Anglin
2003-03-18 18:53 ` John David Anglin
2003-03-14 16:31 ` Joel Soete
2003-03-16 22:52 ` Michael S.Zick
2003-03-16 23:06 ` Matthew Wilcox
2003-03-16 23:17 ` Michael S.Zick
2003-03-20 18:20 ` Joel Soete
2003-03-14 13:17 ` Matthew Wilcox
2003-03-14 12:48 ` Joel Soete
2003-03-20 18:06 ` Joel Soete
2003-03-20 18:06 ` Joel Soete
2003-03-02 4:59 ` Randolph Chung
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=20030302170105.GU11363@tausq.org \
--to=tausq@debian.org \
--cc=debian-hppa@lists.debian.org \
--cc=parisc-linux@lists.parisc-linux.org \
--cc=xam@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.