From: Mike Frysinger <vapier@gentoo.org>
To: Gentoo-Dev <gentoo-dev@gentoo.org>
Subject: Re: [gentoo-dev] Status of gcc-3.2.3-r2[Scanned]
Date: Wed, 17 Sep 2003 16:48:25 -0400 [thread overview]
Message-ID: <200309171648.25893.vapier@gentoo.org> (raw)
In-Reply-To: <1063831275.7832.1064.camel@nosferatu.lan>
[-- Attachment #1: signed data --]
[-- Type: text/plain, Size: 552 bytes --]
On Wednesday 17 September 2003 16:41, Martin Schlemmer wrote:
> For some reason it breaks others boxes badly. I have a -r3 here
> that fix the static linking issues without the bad fix in -r2, as
> well as the parser issues that -r2 also fixed. Over here -r3
> does an bootstrap and emerge system (ok, nptl based) fine, as
> well as busy now with emerge gnome. I will commit it toward
> the end of the week/weekend after one or two more look overs.
are you talking 3.3.1 or 3.2.3 ?
zhen wants 3.2.3, i want 3.3.1 ... cant we have it all ? :(
-mike
[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 827 bytes --]
next prev parent reply other threads:[~2003-09-17 20:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-17 17:49 [gentoo-dev] Status of gcc-3.2.3-r2[Scanned] John Davis
2003-09-17 20:41 ` Martin Schlemmer
2003-09-17 20:48 ` Mike Frysinger [this message]
2003-09-20 18:46 ` Martin Schlemmer
2003-09-20 18:46 ` Martin Schlemmer
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=200309171648.25893.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=gentoo-dev@gentoo.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