Processed: Re: Bug#423733: fixed in gcc-snapshot 20070515-1

Processing commands for [EMAIL PROTECTED]: > reopen 423733 Bug#423733: gcc-snapshot: FTBFS: configure: error: Link tests are not allowed after GCC_NO_EXECUTABLES. 'reopen' may be inappropriate when a bug has been closed with a version; you may need to use 'found' to remove fixed versions. Bug re

Bug#423733: fixed in gcc-snapshot 20070515-1

reopen 423733 thanks Martin Michlmayr writes: >* Disable biarch_archs on i386 and powerpc for now so they will > hopefully build (closes: #423733). why powerpc? why closing, you are just working around the problem. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsu

Bug#420550: marked as done (Segfault in constrain_class_visibility with anonymous namespace)

Your message dated Wed, 16 May 2007 06:32:10 + with message-id <[EMAIL PROTECTED]> and subject line Bug#420550: fixed in gcc-snapshot 20070515-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the c

Bug#419933: marked as done (Segfault in integer_zerop, called via ipa-type-escape.c)

Your message dated Wed, 16 May 2007 06:32:10 + with message-id <[EMAIL PROTECTED]> and subject line Bug#419933: fixed in gcc-snapshot 20070515-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the c

Bug#423733: marked as done (gcc-snapshot: FTBFS: configure: error: Link tests are not allowed after GCC_NO_EXECUTABLES.)

Your message dated Wed, 16 May 2007 06:32:10 + with message-id <[EMAIL PROTECTED]> and subject line Bug#423733: fixed in gcc-snapshot 20070515-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the c

[Bug rtl-optimization/31944] Endless loop while building a 64-bit 2.6.20 kernel

-- tbm at cyrius dot com changed: What|Removed |Added CC||dave dot anglin at nrc dot ||ca

gcc-snapshot_20070515-1_amd64.changes ACCEPTED

Accepted: gcc-snapshot_20070515-1.diff.gz to pool/main/g/gcc-snapshot/gcc-snapshot_20070515-1.diff.gz gcc-snapshot_20070515-1.dsc to pool/main/g/gcc-snapshot/gcc-snapshot_20070515-1.dsc gcc-snapshot_20070515-1_amd64.deb to pool/main/g/gcc-snapshot/gcc-snapshot_20070515-1_amd64.deb gcc-snapsh

Processing of gcc-snapshot_20070515-1_amd64.changes

gcc-snapshot_20070515-1_amd64.changes uploaded successfully to localhost along with the files: gcc-snapshot_20070515-1.dsc gcc-snapshot_20070515.orig.tar.gz gcc-snapshot_20070515-1.diff.gz gcc-snapshot_20070515-1_amd64.deb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE,

Bug#424402: gcc: Endless loop while building a 64-bit 2.6.20 parisc kernel

Package: gcc-4.1 Version: 4:4.1.2-6 Severity: serious Forwarded: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31944 Tags: upstream The build of the 2-6-20-1-parisc64-smp kernel FTBFS because of an endless loop due to what appears to be a gcc issue: http://buildd.debian.org/fetch.cgi?pkg=linux-2.6&

gcc-4.1_4.1.2-7_sparc.changes ACCEPTED

Accepted: cpp-4.1_4.1.2-7_sparc.deb to pool/main/g/gcc-4.1/cpp-4.1_4.1.2-7_sparc.deb fixincludes_4.1.2-7_sparc.deb to pool/main/g/gcc-4.1/fixincludes_4.1.2-7_sparc.deb g++-4.1-multilib_4.1.2-7_sparc.deb to pool/main/g/gcc-4.1/g++-4.1-multilib_4.1.2-7_sparc.deb g++-4.1_4.1.2-7_sparc.deb to

Processing of gcc-4.1_4.1.2-7_sparc.changes

gcc-4.1_4.1.2-7_sparc.changes uploaded successfully to localhost along with the files: gcc-4.1-base_4.1.2-7_sparc.deb libgcc1_4.1.2-7_sparc.deb lib64gcc1_4.1.2-7_sparc.deb cpp-4.1_4.1.2-7_sparc.deb protoize_4.1.2-7_sparc.deb fixincludes_4.1.2-7_sparc.deb libmudflap0_4.1.2-7_sparc.deb

Bug#421354: marked as done ([ia64] ICE in rtl_verify_flow_info, at cfgrtl.c:2050)

Your message dated Tue, 15 May 2007 23:08:59 +0200 with message-id <[EMAIL PROTECTED]> and subject line latent/not a bug has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to

Bug#422971: marked as done (gcc-4.1: FTBFS on arm: Error: junk at end of line, first unrecognized character is `, ')

Your message dated Tue, 15 May 2007 11:19:13 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#422971: gcc-4.1: FTBFS on arm: Error: junk at end of line, has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#423740: Processed: Re: Bug#423740: postgresql-pljava: FTBFS: gcjh: Command not found

Am Montag, 14. Mai 2007 10:28 schrieb Matthias Klose: > please use gjavah, gcjh is obsolete. Where is this documented? Why is there no transition plan? Why does gcjh-4.1 still exist? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTEC

Bug#369690: IMPORTANT COMMUNIQUE!

http://img15.imgspot.com/u/07/134/02/8q.gif Hps gman livethey seem pretty goodno, robertm. Teams estimation quotsweet spotquot. From browser sweet yogui jul. Admin prompt prevent launching rated gamesthe, linked rewritten. Onagain ot nothing discussing grin derailback topictry wed! -- To UNSU

Bug#422971: gcc-4.1: FTBFS on arm: Error: junk at end of line,

shouldn't this copy be closed as well.

Bug#363456: HUGE report

http://www.imagehost.ro/pict//1509061446494dd62f664.gif Described avoids, confusion multiple ensures. Mhzcpu amd, ghz memory mb wddm. Wc compliance systemxml net apps supported downlevel platforms downloaded. Bash title raquo activate xpquick homeselect xpview toarticle? Old were written versio