[gentoo-dev] What to do with GCC 4 related bugs?

[gentoo-dev] What to do with GCC 4 related bugs?

[Dirk Heinrichs]

[-- Attachment #1: Type: text/plain, Size: 613 bytes --]

Hi,

I recently switched to GCC 4.0.2. A handful of packages didn't (re-)compile 
during emerge -e system and emerge -e world. Is there a big GCC 4 related 
bug in bugzilla where I can report those problems or should I write one 
report for each package?

Thanx...

	Dirk
-- 
Dirk Heinrichs          | Tel:  +49 (0)162 234 3408
Configuration Manager   | Fax:  +49 (0)211 47068 111
Capgemini Deutschland   | Mail: dirk.heinrichs@capgemini.com
Hambornerstraße 55      | Web:  http://www.capgemini.com
D-40472 Düsseldorf      | ICQ#: 110037733
GPG Public Key C2E467BB | Keyserver: www.keyserver.net

[-- Attachment #2: Type: application/pgp-signature, Size: 190 bytes --]

Re: [gentoo-dev] What to do with GCC 4 related bugs?

[Chris White]

[-- Attachment #1: Type: text/plain, Size: 488 bytes --]

On Monday 02 January 2006 17:01, Dirk Heinrichs wrote:
> Hi,
>
> I recently switched to GCC 4.0.2. A handful of packages didn't (re-)compile
> during emerge -e system and emerge -e world. Is there a big GCC 4 related
> bug in bugzilla where I can report those problems or should I write one
> report for each package?

The policy is pretty much if it doesn't compile, you get to fix it.  If you 
have a patch then report it to bugzilla.

> Thanx...
>
> 	Dirk

Chris White

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-dev] What to do with GCC 4 related bugs?

[Mark Loeser]

[-- Attachment #1: Type: text/plain, Size: 934 bytes --]

Chris White <chriswhite@gentoo.org> said:
> On Monday 02 January 2006 17:01, Dirk Heinrichs wrote:
> > Hi,
> >
> > I recently switched to GCC 4.0.2. A handful of packages didn't (re-)compile
> > during emerge -e system and emerge -e world. Is there a big GCC 4 related
> > bug in bugzilla where I can report those problems or should I write one
> > report for each package?
> 
> The policy is pretty much if it doesn't compile, you get to fix it.  If you 
> have a patch then report it to bugzilla.

Actually, since I plan on moving this to ~arch soon, please report all bugs
to us, even if you don't have a patch.  I'd like to know of everything that
is broken.

-- 
Mark Loeser   -   Gentoo Developer (cpp gcc-porting toolchain x86)
email         -   halcy0n AT gentoo DOT org
                  mark AT halcy0n DOT com
web           -   http://dev.gentoo.org/~halcy0n/
                  http://www.halcy0n.com

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-dev] What to do with GCC 4 related bugs?

[Dirk Heinrichs]

[-- Attachment #1: Type: text/plain, Size: 809 bytes --]

Am Montag, 2. Januar 2006 21:45 schrieb ext Mark Loeser:

> Chris White <chriswhite@gentoo.org> said:
> > The policy is pretty much if it doesn't compile, you get to fix it.  If
> > you have a patch then report it to bugzilla.

> Actually, since I plan on moving this to ~arch soon, please report all
> bugs to us, even if you don't have a patch.  I'd like to know of
> everything that is broken.

OK, expect the reports within the next few hours.

Bye...

	Dirk
-- 
Dirk Heinrichs          | Tel:  +49 (0)162 234 3408
Configuration Manager   | Fax:  +49 (0)211 47068 111
Capgemini Deutschland   | Mail: dirk.heinrichs@capgemini.com
Hambornerstraße 55      | Web:  http://www.capgemini.com
D-40472 Düsseldorf      | ICQ#: 110037733
GPG Public Key C2E467BB | Keyserver: www.keyserver.net

[-- Attachment #2: Type: application/pgp-signature, Size: 190 bytes --]

Re: [gentoo-dev] What to do with GCC 4 related bugs?

[Mike Frysinger]

On Tuesday 03 January 2006 01:43, Dirk Heinrichs wrote:
> Am Montag, 2. Januar 2006 21:45 schrieb ext Mark Loeser:
> > Chris White <chriswhite@gentoo.org> said:
> > > The policy is pretty much if it doesn't compile, you get to fix it.  If
> > > you have a patch then report it to bugzilla.
> >
> > Actually, since I plan on moving this to ~arch soon, please report all
> > bugs to us, even if you don't have a patch.  I'd like to know of
> > everything that is broken.
>
> OK, expect the reports within the next few hours.
>
> Bye...

just make sure you search to see if one hasnt already been filed ;)
-mike
-- 
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] What to do with GCC 4 related bugs?

[Dirk Heinrichs]

[-- Attachment #1: Type: text/plain, Size: 836 bytes --]

Am Montag, 2. Januar 2006 21:45 schrieb ext Mark Loeser:

> Actually, since I plan on moving this to ~arch soon, please report all
> bugs to us, even if you don't have a patch.  I'd like to know of
> everything that is broken.

I filed bug reports for crypto++, botan, monotone and isdn4k-utils. Still 
have to verify wether OpenOffice.org emerge failure is GCC 4 related or 
not, but this I will do over the weekend.

The bug numbers are: 117547, 117548, 117572 and 117573.

Bye...

	Dirk
-- 
Dirk Heinrichs          | Tel:  +49 (0)162 234 3408
Configuration Manager   | Fax:  +49 (0)211 47068 111
Capgemini Deutschland   | Mail: dirk.heinrichs@capgemini.com
Hambornerstraße 55      | Web:  http://www.capgemini.com
D-40472 Düsseldorf      | ICQ#: 110037733
GPG Public Key C2E467BB | Keyserver: www.keyserver.net

[-- Attachment #2: Type: application/pgp-signature, Size: 190 bytes --]

Re: [gentoo-dev] What to do with GCC 4 related bugs?

[Bjarke Istrup Pedersen]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Dirk Heinrichs skrev:
> Am Montag, 2. Januar 2006 21:45 schrieb ext Mark Loeser:
> 
> 
>>Actually, since I plan on moving this to ~arch soon, please report all
>>bugs to us, even if you don't have a patch.  I'd like to know of
>>everything that is broken.
> 
> 
> I filed bug reports for crypto++, botan, monotone and isdn4k-utils. Still 
> have to verify wether OpenOffice.org emerge failure is GCC 4 related or 
> not, but this I will do over the weekend.
> 
> The bug numbers are: 117547, 117548, 117572 and 117573.
> 
> Bye...
> 
> 	Dirk

Is there a metabug where we can keep track of all the GCC 4 bugs?
If so, what bug # ?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFDuqemO+Ewtpi9rLERAo1DAJ9N4zVXqtBBzqpiufQHElqY72rDZQCeIDbj
kwN/wVgJUGwPPGops+vVJis=
=zgOW
-----END PGP SIGNATURE-----
-- 
gentoo-dev@gentoo.org mailing list

Re[2]: [gentoo-dev] What to do with GCC 4 related bugs?

[Jakub Moc]

[-- Attachment #1: Type: text/plain, Size: 455 bytes --]


3.1.2006, 17:34:46, Bjarke Istrup Pedersen wrote:

> Is there a metabug where we can keep track of all the GCC 4 bugs?
> If so, what bug # ?

Sure - http://bugs.gentoo.org/show_bug.cgi?id=117482


--
Best regards,

 Jakub Moc
 mailto:jakub@gentoo.org
 GPG signature: http://subkeys.pgp.net:11371/pks/lookup?op=get&search=0xCEBA3D9E
 Primary key fingerprint: D2D7 933C 9BA1 C95B 2C95  B30F 8717 D5FD CEBA 3D9E

 ... still no signature ;)

[-- Attachment #2: Type: application/pgp-signature, Size: 183 bytes --]

Re: [gentoo-dev] What to do with GCC 4 related bugs?

[Diego 'Flameeyes' Pettenò]

[-- Attachment #1: Type: text/plain, Size: 751 bytes --]

On Monday 02 January 2006 09:01, Dirk Heinrichs wrote:
> I recently switched to GCC 4.0.2. A handful of packages didn't (re-)compile
> during emerge -e system and emerge -e world. Is there a big GCC 4 related
> bug in bugzilla where I can report those problems or should I write one
> report for each package?
Usually, one report for each package is the preferred way, as this allows to 
close the bugs already committed, and to dupe against existing if it's the 
case (always search for existing bugs of course).

I'm wondering if a gcc4 tracker bug might help as Mark was planning to move it 
in ~arch.

-- 
Diego "Flameeyes" Pettenò - http://dev.gentoo.org/~flameeyes/
Gentoo/ALT lead, Gentoo/FreeBSD, Video, AMD64, Sound, PAM, KDE

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-dev] What to do with GCC 4 related bugs?

[Mark Loeser]

[-- Attachment #1: Type: text/plain, Size: 1100 bytes --]

Diego 'Flameeyes' Pettenò <flameeyes@gentoo.org> said:
> On Monday 02 January 2006 09:01, Dirk Heinrichs wrote:
> > I recently switched to GCC 4.0.2. A handful of packages didn't (re-)compile
> > during emerge -e system and emerge -e world. Is there a big GCC 4 related
> > bug in bugzilla where I can report those problems or should I write one
> > report for each package?
> Usually, one report for each package is the preferred way, as this allows to 
> close the bugs already committed, and to dupe against existing if it's the 
> case (always search for existing bugs of course).

Yea, one report per package please, its much easier.

> I'm wondering if a gcc4 tracker bug might help as Mark was planning to move it
> in ~arch.

Sounds like a good idea.  I'll probably make one in a bit if someone doesn't
beat me to it.

-- 
Mark Loeser   -   Gentoo Developer (cpp gcc-porting toolchain x86)
email         -   halcy0n AT gentoo DOT org
                  mark AT halcy0n DOT com
web           -   http://dev.gentoo.org/~halcy0n/
                  http://www.halcy0n.com

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]