Bug#369810: FTBFS on alpha: ICE in spill_failure, at reload1.c:1911

2006-06-01 Thread Martin Michlmayr
Package: gcc-snapshot Version: 20060530-1 Severity: important gcc 4.2 no longer builds on Alpha since an ICE occurs when building classpath. This is PR27858. if /bin/sh ../../libtool --mode=compile /build/buildd/gcc-snapshot-20060530/build/./gcc/xgcc

Bug#369817: [4.0,4.1,4.2 regression][mips] ICE in expand_expr_real_1, at expr.c:6864

2006-06-01 Thread Martin Michlmayr
Package: gcc-4.0 Version: 4.0.3-3 This ICE occurs with gcc 4.0, 4.1, 4.2, but not with 3.4. PR27861 Automatic build of gdb_6.4-1 on swarm by sbuild/mipsel 0.45 ... cc -c -DHAVE_CONFIG_H -DPROFILE=1 -DWITH_PROFILE=-1 -DWITH_ALIGNMENT=NONSTRICT_ALIGNMENT -DWITH_TARGET_WORD_BITSIZE=32

Processed: Re: Bug#365934: java-gcj-compat-dev: Dead links in /usr/lib/jvm/java-gcj/include/

2006-06-01 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: reopen 365934 Bug#365934: java-gcj-compat-dev: Dead links in /usr/lib/jvm/java-gcj/include/ 'reopen' is deprecated when a bug has been closed with a version; use 'found' or 'submitter' as appropriate instead. Bug reopened, originator not changed. stop

Bug#365934: java-gcj-compat-dev: Dead links in /usr/lib/jvm/java-gcj/include/

2006-06-01 Thread Peter Eisentraut
reopen 365934 stop If you choose to resolve this by tightening the dependency on gcj, then the dependency needs to look something like gcj-4.1 (= 4.1.1), gcj-4.1 ( 4.1.2) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#365934: java-gcj-compat-dev: Dead links in /usr/lib/jvm/java-gcj/include/

2006-06-01 Thread Matthias Klose
Peter Eisentraut writes: reopen 365934 stop If you choose to resolve this by tightening the dependency on gcj, then the dependency needs to look something like gcj-4.1 (= 4.1.1), gcj-4.1 ( 4.1.2) wrong. the latter version is unknown. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with

Bug#365934: java-gcj-compat-dev: Dead links in /usr/lib/jvm/java-gcj/include/

2006-06-01 Thread Matthias Klose
tags 365934 +etch merge 365934 367038 thanks Peter Eisentraut writes: Am Donnerstag, 1. Juni 2006 16:58 schrieb Matthias Klose: Peter Eisentraut writes: reopen 365934 stop If you choose to resolve this by tightening the dependency on gcj, then the dependency needs to look

Bug#365934: java-gcj-compat-dev: Dead links in /usr/lib/jvm/java-gcj/include/

2006-06-01 Thread Peter Eisentraut
Am Donnerstag, 1. Juni 2006 16:58 schrieb Matthias Klose: Peter Eisentraut writes: reopen 365934 stop If you choose to resolve this by tightening the dependency on gcj, then the dependency needs to look something like gcj-4.1 (= 4.1.1), gcj-4.1 ( 4.1.2) wrong. the latter version

Processed: Re: Bug#365934: java-gcj-compat-dev: Dead links in /usr/lib/jvm/java-gcj/include/

2006-06-01 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: tags 365934 +etch Bug#365934: java-gcj-compat-dev: Dead links in /usr/lib/jvm/java-gcj/include/ There were no tags set. Tags added: etch merge 365934 367038 Bug#365934: java-gcj-compat-dev: Dead links in /usr/lib/jvm/java-gcj/include/ Bug#367038:

Bug#365934: java-gcj-compat-dev: Dead links in /usr/lib/jvm/java-gcj/include/

2006-06-01 Thread Matthias Klose
Peter Eisentraut writes: Am Donnerstag, 1. Juni 2006 16:58 schrieb Matthias Klose: Peter Eisentraut writes: reopen 365934 stop If you choose to resolve this by tightening the dependency on gcj, then the dependency needs to look something like gcj-4.1 (= 4.1.1), gcj-4.1 (

Processed: forwarded

2006-06-01 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: tags 369817 + upstream Bug#369817: [4.0,4.1,4.2 regression][mips] ICE in expand_expr_real_1, at expr.c:6864 There were no tags set. Tags added: upstream forwarded 369817 http://gcc.gnu.org/PR27861 Bug#369817: [4.0,4.1,4.2 regression][mips] ICE in

Bug#361715: Debian bug 361715 followup

2006-06-01 Thread Bdale Garbee
I have several questions for those of you seeing this problem, to try and get to the root cause. I don't use amcheck in cron myself, so could use your help chasing down the problem. First, have any of you tried the 2.5.0p2-1 amanda-server package yet? I don't see anything in the upstream

[bts-link] source package gcc-4.0

2006-06-01 Thread bts-link-upstream
# # bts-link upstream status pull for source package gcc-4.0 # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user [EMAIL PROTECTED] # remote status report for #369817 # * http://gcc.gnu.org/PR27861 # * remote status changed: (?) - UNCONFIRMED usertags 369817 +

[bts-link] source package gcc-snapshot

2006-06-01 Thread bts-link-upstream
# # bts-link upstream status pull for source package gcc-snapshot # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user [EMAIL PROTECTED] # remote status report for #369810 # * http://gcc.gnu.org/PR27858 # * remote status changed: (?) - NEW usertags 369810 +

Processed: [bts-link] source package gcc-snapshot

2006-06-01 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: # # bts-link upstream status pull for source package gcc-snapshot # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user [EMAIL PROTECTED] Setting user to [EMAIL PROTECTED] (was [EMAIL PROTECTED]). # remote status report

Bug#369873: gcj-4.1: fails to import package from project

2006-06-01 Thread Christian Holm Christensen
Package: gcj-4.1 Version: 4.1.0-2j1 Severity: important *** Please type your report below this line *** GCJ fails with Can't find default package 'core'. ... when a class source file specifies `import core.*'. A full example is outlined below. Suppose we have the directory structure

Bug#361608: marked as done (ecj-bootstrap: takes over /usr/lib/jvm/java-gcj/bin/javac with ../../../../bin/ecj)

2006-06-01 Thread Debian Bug Tracking System
Your message dated Thu, 01 Jun 2006 21:17:47 -0700 with message-id [EMAIL PROTECTED] and subject line Bug#361608: fixed in ecj-bootstrap 3.1.2-6 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

Bug#361806: marked as done (java-gcj-compat-dev: Can't build with javac)

2006-06-01 Thread Debian Bug Tracking System
Your message dated Thu, 01 Jun 2006 21:17:47 -0700 with message-id [EMAIL PROTECTED] and subject line Bug#361806: fixed in ecj-bootstrap 3.1.2-6 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