public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: David Nielsen <Lovechild@foolclan.com>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] [WIP]  gcc 3.3
Date: 16 May 2003 17:38:40 +0200	[thread overview]
Message-ID: <1053099520.16399.2.camel@pilot.stavtrup-st.dk> (raw)
In-Reply-To: <20030516162025.7090a0ef.spider@gentoo.org>

Just FYI, a few brave souls like myself have already been running GCC
3.3 of CVS for a period of time, and have found quite a few solutions to
common problems with GCC 3.3 and various packages.

There's a thread in Other things Gentoo on the forums that you might
want to read, I forgot the complete link and I lack a browser right now
so go search :)

On Fri, 2003-05-16 at 16:20, Spider wrote:
> begin  quote
> On 16 May 2003 13:00:53 +0100
> Dhruba Bandopadhyay <dhruba@codewordt.co.uk> wrote:
> > 
> > There is an ebuild for it on bugzilla and one here and some on forums
> > too.  Have you used any of these as a definitive base or is this a new
> > creation?
> 
> Neither, I wanted a go at it again (I haven't been messing with gcc
> since 3.1 days)  so I started from last known working 3.2.3 and went on.
>  
> > Also, is there any sign of this being entered into hardmasked or
> > testig state on portage?
> 
> I'm not the maintainer of gcc, so I shall leave that up to Azarah to
> decide, let him distill the different builds along with his own
> experience to see what goes.   
> 
> > 
> > I'd be quite keen on testing it out since I have had my fair share of
> > pentium4 problems and am desperately hoping an upgrade of gcc will
> > sort them out.
> 
> It may, so far it appears some old c++ code will barf though. not sure
> about glibc and kernel issues either. 
> 
> > 
> > Pardon my ignorance but have all these patches been commented out to
> > prevent resultant problems or because they are no longer necessary?
> 
> Thats up to the maintainer, since I havent taken the time to go through
> the patches each in turn and verify wether it is needed anymore I just
> commented it out to see what happened.  I suspect a lot of them are no
> longer necessary, and those that are will have to be re-diffed in a new
> manner, not really an easy task.
> 
> I suspect the real build won't enter portage until propolice is up in
> speed though.
> 
> //Spider
> 


--
gentoo-dev@gentoo.org mailing list


  reply	other threads:[~2003-05-16 15:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-16  0:20 [gentoo-dev] [WIP] gcc 3.3 Spider
2003-05-16  0:24 ` 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 [this message]
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=1053099520.16399.2.camel@pilot.stavtrup-st.dk \
    --to=lovechild@foolclan.com \
    --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