gcc-4.1 4.1.1-11 MIGRATED to testing

FYI: The status of the gcc-4.1 source package in Debian's testing distribution has changed. Previous version: 4.1.1-5 Current version: 4.1.1-11 -- This email is automatically generated; [EMAIL PROTECTED] is responsible. See http://people.debian.org/~henning/trille/ for more information. -

Bug#385306: Log for failed build of shaperd_0.2.1-5 (dist=unstable1)

one more (but fixed upstream now): > Automatic build of shaperd_0.2.1-5 on swarm by sbuild/mipsel 0.45 ... > D: Running: /usr/lib/gcc-snapshot/bin/g++ -Wall -ftree-vectorize -Os > -I/usr/src/linux/include -I/usr/include/libipq -DWITH_IPQ -c config.cpp > In file included from > /usr/lib/gcc-snap

Al-Manahel Newsletter List Unsubscription

The removal of the email address: [EMAIL PROTECTED] >From the mailing list: Al-Manahel Newsletter List is all set. Date of this removal: Fri Sep 1 10:42:00 2006 Please save this email message for future reference. --

[Bug libgcj/28698] [gcj] libgcj-bc only used when building shared libs, not executables

--- Comment #10 from tromey at gcc dot gnu dot org 2006-09-01 16:16 --- Subject: Bug 28698 Author: tromey Date: Fri Sep 1 16:16:15 2006 New Revision: 116631 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=116631 Log: PR libgcj/28698: * libgcj_bc.c (DECLARE_PRIM_T

Bug#384036: marked as done (gcc-4.1: Contains non-free documentation)

Your message dated Fri, 01 Sep 2006 07:02:54 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#384036: fixed in gcc-4.1 4.1.1ds1-12 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 no

Bug#383705: marked as done (please provide debugging symbols somewhere)

Your message dated Fri, 01 Sep 2006 07:02:53 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#383705: fixed in gcc-4.1 4.1.1ds1-12 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 no

Bug#344041: marked as done ([m68k] gcc-4.0: internal consistency failure)

Your message dated Fri, 01 Sep 2006 07:02:51 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#344041: fixed in gcc-4.1 4.1.1ds1-12 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 no

Bug#323426: marked as done ([m68k] ICE: gcc-4.0 segfaults with -O2 dealing with long doubles)

Your message dated Fri, 01 Sep 2006 07:02:50 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#323426: fixed in gcc-4.1 4.1.1ds1-12 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 no

Bug#378599: marked as done ([m68k] gcc-4.1 -O2 optimization problem)

Your message dated Fri, 01 Sep 2006 07:02:53 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#378599: fixed in gcc-4.1 4.1.1ds1-12 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 no

Bug#364820: marked as done (Add /usr/lib/jni to the default java.library.path)

Your message dated Fri, 01 Sep 2006 07:02:51 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#364820: fixed in gcc-4.1 4.1.1ds1-12 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 no

Bug#345574: marked as done ([PR25642][m68k] optimizer bug: registers are clobbered but not restored)

Your message dated Fri, 01 Sep 2006 07:02:51 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#345574: fixed in gcc-4.1 4.1.1ds1-12 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 no

Bug#340293: marked as done ([PR 24912][m68k] ICE reload_cse_simplify_operands)

Your message dated Fri, 01 Sep 2006 07:02:50 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#340293: fixed in gcc-4.1 4.1.1ds1-12 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 no

Bug#356548: marked as done (FTBFS with G++ 4.1: on mips: error: cannot bind packed field)

Your message dated Fri, 01 Sep 2006 07:02:51 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#356548: fixed in gcc-4.1 4.1.1ds1-12 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 no

gcc-4.1 override disparity

There are disparities between your recently accepted upload and the override file for the following file(s): gcc-4.1-base_4.1.1-13_i386.deb: package says section is libs, override says devel. gcc-4.1-base_4.1.1-13_powerpc.deb: package says section is libs, override says devel. libssp0_4.1.1-13_i

Processing of gcc-4.1_4.1.1ds1-13_multi.changes

gcc-4.1_4.1.1ds1-13_multi.changes uploaded successfully to localhost along with the files: gobjc++-4.1_4.1.1-13_powerpc.deb lib64gfortran1_4.1.1-13_i386.deb gcc-4.1-base_4.1.1-13_powerpc.deb libgcc1_4.1.1-13_i386.deb libobjc1_4.1.1-13_i386.deb libffi4_4.1.1-13_powerpc.deb libstdc++6-4

gcc-4.1_4.1.1ds1-13_multi.changes ACCEPTED

Accepted: cpp-4.1_4.1.1-13_i386.deb to pool/main/g/gcc-4.1/cpp-4.1_4.1.1-13_i386.deb cpp-4.1_4.1.1-13_powerpc.deb to pool/main/g/gcc-4.1/cpp-4.1_4.1.1-13_powerpc.deb fastjar_4.1.1-13_i386.deb to pool/main/g/gcc-4.1/fastjar_4.1.1-13_i386.deb fastjar_4.1.1-13_powerpc.deb to pool/main/g/gcc-4

Processing of gcc-4.1_4.1.1ds1-12_multi.changes

gcc-4.1_4.1.1ds1-12_multi.changes uploaded successfully to localhost along with the files: lib64stdc++6_4.1.1-12_powerpc.deb lib64mudflap0_4.1.1-12_powerpc.deb lib64ssp0_4.1.1-12_powerpc.deb treelang-4.1_4.1.1-12_m68k.deb libgcc1_4.1.1-12_powerpc.deb libmudflap0-dev_4.1.1-12_m68k.deb

gcc-4.1 override disparity

There are disparities between your recently accepted upload and the override file for the following file(s): gcc-4.1-base_4.1.1-12_m68k.deb: package says section is libs, override says devel. gcc-4.1-base_4.1.1-12_powerpc.deb: package says section is libs, override says devel. libssp0_4.1.1-12_m

gcc-4.1_4.1.1ds1-12_multi.changes ACCEPTED

Accepted: cpp-4.1_4.1.1-12_m68k.deb to pool/main/g/gcc-4.1/cpp-4.1_4.1.1-12_m68k.deb cpp-4.1_4.1.1-12_powerpc.deb to pool/main/g/gcc-4.1/cpp-4.1_4.1.1-12_powerpc.deb fastjar_4.1.1-12_m68k.deb to pool/main/g/gcc-4.1/fastjar_4.1.1-12_m68k.deb fastjar_4.1.1-12_powerpc.deb to pool/main/g/gcc-4

Bug#385580: gcc generates incorrect code on s390

reassign 385580 gcc-4.1 clone 385580 -1 reassign -1 coreutils severity 385580 important forwarded 385580 http://gcc.gnu.org/PR28146 retitle 385580 [4.1 regression, fixed in 4.2] gcc generates incorrect code on s390 tags 385580 + upstream tags 385580 + fixed-upstream thanks according to PR 28789 t

Processed: Re: Bug#385580: gcc generates incorrect code on s390

Processing commands for [EMAIL PROTECTED]: > reassign 385580 gcc-4.1 Bug#385580: gcc generates incorrect code on s390 Bug reassigned from package `gcc' to `gcc-4.1'. > clone 385580 -1 Bug#385580: gcc generates incorrect code on s390 Bug 385580 cloned as bug 385582. > reassign -1 coreutils Bug#38

Bug#385580: gcc generates incorrect code on s390

Severity: serious Package: gcc gcc has been building parts of coreutils on s390 (sha384 & sha512) in a way that silently generates incorrect results. (Caught by tests during the coreutils build process.) This has been traced to a bug in gcc: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id