From: Spider <spider@gentoo.org>
To: gentoo-dev <gentoo-dev@gentoo.org>
Cc: azarah@gentoo.org
Subject: [gentoo-dev] [WIP] gcc 3.3
Date: Fri, 16 May 2003 02:20:31 +0200 [thread overview]
Message-ID: <20030516022031.57157e45.spider@gentoo.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 657 bytes --]
hi folks,
here is an initial ebuild of gcc 3.3, it doesn't contain propolice
patch, and I haven't checked it with "build" or other flags except the
default. (its slow to build on this machine)
The installationprocess has changed significantly, and now is actually
far cleaner. I hope there aren't many snags with how this behaves on
systems.
I haven't yet looked at the thread patches, I hope somone who's more
into this than I am can advice on that.
Comments and testers are welcome :)
//Spider
--
begin .signature
This is a .signature virus! Please copy me into your .signature!
See Microsoft KB Article Q265230 for more information.
end
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2003-05-16 0:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-16 0:20 Spider [this message]
2003-05-16 0:24 ` [gentoo-dev] [WIP] gcc 3.3 Spider
2003-05-16 0:32 ` Spider
2003-05-16 12:00 ` Dhruba Bandopadhyay
2003-05-16 14:20 ` Spider
2003-05-16 15:38 ` David Nielsen
2003-05-16 15:38 ` David Nielsen
2003-05-16 19:58 ` 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=20030516022031.57157e45.spider@gentoo.org \
--to=spider@gentoo.org \
--cc=azarah@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