public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Michael Odell" <michael@michaelodell.net>
To: <gentoo-dev@gentoo.org>
Subject: RE: [gentoo-dev] Gcc 3.0.4 installed system
Date: Sat, 6 Apr 2002 12:13:41 -0700	[thread overview]
Message-ID: <001e01c1dd9f$2a8bd430$0300a8c0@Darkstar> (raw)
In-Reply-To: <20020406101237.U26184-100000@shell.phattydomain.com>

Thanks Geert!  gcc 3.x is also required for compiling GNUstep, which I
had been hoping to try with Gentoo.  You've made it possible :)

Thanks,

Michael Odell

-----Original Message-----
From: gentoo-dev-admin@gentoo.org [mailto:gentoo-dev-admin@gentoo.org]
On Behalf Of Joe Oppegaard
Sent: Saturday, April 06, 2002 11:18 AM
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Gcc 3.0.4 installed system

On Sat, 6 Apr 2002, Bart Verwilst wrote:

> Hmm..
>
> Great that gentoo is now gcc3.x compliant :o)
> But what are the advantages of using gcc 3.x over gcc 2.95.x?
> Isn't gcc 3.x slower than 2.95?

One of the advantages of gcc 3.x is that it has special optimizations
for
Athlon processors. Other then that, I'm not too familiar with gcc 3.x.


>
> Thanks, great work!
>
> On Saturday 06 April 2002 14:01, Geert Bevin wrote:
> || Hi all,
> ||
> || I finally installed 1.0 from scratch and decided to try it out with
gcc
> || 3.0.4 instead of 2.95.3. Along the way I encountered some problems,
but
> || surprisingly little. I've fixed everything that needed fixing and
sadly
> || some packages are backwards incompatible. For that reason and for
the
> || ease of maintenance I've created a dedicated gcc 3 profile.
> ||
> || So, for those that want to try this out, just link the
default-1.0-gcc3
> || profile instead of default-1.0 to /etc/make.profile. Note that this
will
> || only work for installations from scratch and not for updates since
> || applications that link against libstdc++ v2 require the libraries
of gcc
> || v2 and not gcc v3.
> ||
> || There are still some packages that don't compile such as galeon and
> || openjade, but these will be fixed in a matter of time since I need
them
> || ;-) Feel free to submit fixes too.
> ||
> || Best regards,
> ||
> || Geert Bevin
>
> --
> Bart Verwilst
> Gentoo Linux Developer, Desktop Team
> Gent, Belgium
> _______________________________________________
> gentoo-dev mailing list
> gentoo-dev@gentoo.org
> http://lists.gentoo.org/mailman/listinfo/gentoo-dev
>

--
-Joe Oppegaard
http://joppegaard.com

_______________________________________________
gentoo-dev mailing list
gentoo-dev@gentoo.org
http://lists.gentoo.org/mailman/listinfo/gentoo-dev



  reply	other threads:[~2002-04-06 19:13 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-06 12:01 [gentoo-dev] Gcc 3.0.4 installed system Geert Bevin
2002-04-06 14:06 ` Bart Verwilst
2002-04-06 18:18   ` Joe Oppegaard
2002-04-06 19:13     ` Michael Odell [this message]
2002-04-06 22:43     ` Jared H. Hudson
2002-04-07  3:29 ` Preston A. Elder
2002-04-07 10:02   ` Bart Verwilst
2002-04-07 10:49     ` Preston A. Elder
2002-04-07 18:18       ` Stacey Keast
2002-04-07 10:14   ` Geert Bevin
2002-04-07 10:40     ` Preston A. Elder
2002-04-07 10:57       ` Geert Bevin
2002-04-07 12:38       ` Christian Hergl
2002-04-07 12:50         ` Geert Bevin
2002-04-07 22:04 ` Spider
  -- strict thread matches above, loose matches on Subject: below --
2002-04-07  3:10 michael

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='001e01c1dd9f$2a8bd430$0300a8c0@Darkstar' \
    --to=michael@michaelodell.net \
    --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