sm-discuss AT lists.ibiblio.org
Subject: Public SourceMage Discussion List
List archive
- From: Daniel Goller <dgoller AT satx.rr.com>
- To: sm-discuss AT lists.ibiblio.org
- Subject: Re: [SM-Discuss] Status of gcc 4.1
- Date: Sat, 9 Dec 2006 08:25:42 -0600
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Fri, 08 Dec 2006 23:28:48 +0000
Flavien Bridault <vlaaad AT sourcemage.org> wrote:
> Le mercredi 06 décembre 2006 à 01:00 +0100, "Andraž 'ruskie' Levstik" a
> écrit :
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > I've got a FRESHLY BUILT/REBUILT/REBUILT/REBUILT system with:
> > glibc2.5, gcc4.1.1
> >
> > And I had no problems so far....
> >
> Well I'm glad it does not work well only for me... Nobody complains
> actually, so I would say let's put it in test to get a larger feedback ?
> Anyway I'm pretty sure we will have very few bugs.
>
Well, considering how often we force gcc3.4 we should not be too proud of
being able to use gcc4.1.
For what it's worth, what hasn't been forced does play fine with gcc4.1, and
has done so for months.
Have nothing to say to glibc2.5, since i haven't touched it.
We could either remove all the forcing of gcc3.4 first, and then determine
which needs 4.1 patches, or test things against 4.0 and 4.1 at the time we do
remove the forcing.
There is nothing wrong with 4.1, some code does trigger a few extra
sloppyness indicators that even 4.0 still let's fly, but it's not a lot.
To make things smoother in the future the forcing of gcc version below what
is in test must be discouraged, things do not get fixed that way.
This way a rebuild working actually has meaning.
We should move forward with gcc/glibc, and encourage to have the gcc3.4
forcing removed next time people touch a spell that does it. (After testing
it of course.)
Upstream might long have fixed what caused the gcc3.4 forcing. If not we find
what other distros might long have in place for that package.
Daniel
> > - --
> > Andraž "ruskie" Levstik
> > Source Mage GNU/Linux Games grimoire guru
> > Geek/Hacker/Tinker
> >
> > Hacker FAQ: http://www.plethora.net/%7eseebs/faqs/hacker.html
> > Be sure brain is in gear before engaging mouth.
> >
> > Key id = A7A9E461
> > Key fingerprint = 757E C16B F5B7 DC27 B003 CCED CF95 3A77 A7A9 E461
> >
> > -----BEGIN PGP SIGNATURE-----
> > Version: GnuPG v1.4.5 (GNU/Linux)
> >
> > iD8DBQFFdgg5grQX1TBnUh4RAr2eAJ91SynRY1Q8FmOsqqrwV2G0HlFjpQCgps4R
> > rcu63xuB6BDqhYSwxh7L+pg=
> > =4q6m
> > -----END PGP SIGNATURE-----
> > _______________________________________________
> > SM-Discuss mailing list
> > SM-Discuss AT lists.ibiblio.org
> > http://lists.ibiblio.org/mailman/listinfo/sm-discuss
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
iD8DBQFFesdt+HaycIPdpbkRArwqAKCi1ClF7goU9PkvfvU63SnV5Vg0CACgkw4f
dZr01Utc/TzjhoI/ihA6GqQ=
=HPNk
-----END PGP SIGNATURE-----
-
[SM-Discuss] Status of gcc 4.1,
Flavien Bridault, 12/05/2006
-
Re: [SM-Discuss] Status of gcc 4.1,
Jaka Kranjc, 12/05/2006
-
Re: [SM-Discuss] Status of gcc 4.1,
Flavien Bridault, 12/05/2006
- Re: [SM-Discuss] Status of gcc 4.1, Jeremy A. Kolb, 12/05/2006
-
Re: [SM-Discuss] Status of gcc 4.1,
Thomas Orgis, 12/05/2006
-
Re: [SM-Discuss] Status of gcc 4.1,
Andraž 'ruskie' Levstik, 12/05/2006
-
Re: [SM-Discuss] Status of gcc 4.1,
Flavien Bridault, 12/08/2006
-
Re: [SM-Discuss] Status of gcc 4.1,
Daniel Goller, 12/09/2006
- Re: [SM-Discuss] Status of gcc 4.1, Pieter Lenaerts, 12/09/2006
- Re: [SM-Discuss] Status of gcc 4.1, Flavien Bridault, 12/09/2006
- Re: [SM-Discuss] Status of gcc 4.1, Daniel Goller, 12/09/2006
- Re: [SM-Discuss] Status of gcc 4.1, Pieter Lenaerts, 12/10/2006
- Re: [SM-Discuss] Status of gcc 4.1, Daniel Goller, 12/10/2006
- Re: [SM-Discuss] Status of gcc 4.1, Ladislav Hagara, 12/10/2006
- Re: [SM-Discuss] Status of gcc 4.1, seth, 12/10/2006
- Re: [SM-Discuss] Status of gcc 4.1, Ladislav Hagara, 12/11/2006
- Re: [SM-Discuss] Status of gcc 4.1, Andrew Stitt, 12/11/2006
- Re: [SM-Discuss] Status of gcc 4.1, Daniel Goller, 12/11/2006
-
Re: [SM-Discuss] Status of gcc 4.1,
Daniel Goller, 12/09/2006
-
Re: [SM-Discuss] Status of gcc 4.1,
Flavien Bridault, 12/08/2006
-
Re: [SM-Discuss] Status of gcc 4.1,
Andraž 'ruskie' Levstik, 12/05/2006
-
Re: [SM-Discuss] Status of gcc 4.1,
Flavien Bridault, 12/05/2006
-
Re: [SM-Discuss] Status of gcc 4.1,
Jaka Kranjc, 12/05/2006
Archive powered by MHonArc 2.6.24.