From: Randolph Chung <tausq@debian.org>
To: John David Anglin <dave@hiauly1.hia.nrc.ca>
Cc: Matthias Klose <doko@cs.tu-berlin.de>,
debian-hppa@lists.debian.org, debian-gcc@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, 9 Mar 2003 12:45:34 -0800 [thread overview]
Message-ID: <20030309204534.GH11363@tausq.org> (raw)
In-Reply-To: <200303092027.h29KR1pk026585@hiauly1.hia.nrc.ca>
> Did you configure 3.3 using "--enable-sjlj-exceptions=yes"? That way
> the 3.3 C++ library should be compatible with the previous 3.3 library.
> The switch to dwarf2 can be delayed until the next debian release.
yeah, i exchanged some mail with Matthias about this.
Anyway, I have the debs installed in a chroot now. Will start building
random stuff and see what happens :)
stay tuned,
randolph
--
Randolph Chung
Debian GNU/Linux Developer, hppa/ia64 ports
http://www.tausq.org/
next prev parent reply other threads:[~2003-03-09 20:50 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 4:59 ` Randolph Chung
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
2003-03-02 18:50 ` John David Anglin
2003-03-02 18:50 ` John David Anglin
2003-03-02 5:40 ` 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:17 ` John David Anglin
2003-03-03 16:24 ` Randolph Chung
2003-03-03 17:22 ` Joel Soete
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 [this message]
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: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-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 12:44 ` Joel Soete
2003-03-21 13:36 ` Matthew Wilcox
2003-03-21 15:07 ` Joel Soete
2003-03-20 18:23 ` John David Anglin
2003-03-18 20:55 ` 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-12 17:53 ` Joel Soete
2003-03-12 17:35 ` 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=20030309204534.GH11363@tausq.org \
--to=tausq@debian.org \
--cc=dave@hiauly1.hia.nrc.ca \
--cc=debian-gcc@lists.debian.org \
--cc=debian-hppa@lists.debian.org \
--cc=doko@cs.tu-berlin.de \
--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 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.