gcc-4.0_4.0.0ds2-12_powerpc.changes ACCEPTED

2005-07-06 Thread Debian Installer
Accepted: cpp-4.0_4.0.0-12_powerpc.deb to pool/main/g/gcc-4.0/cpp-4.0_4.0.0-12_powerpc.deb fastjar_4.0.0-12_powerpc.deb to pool/main/g/gcc-4.0/fastjar_4.0.0-12_powerpc.deb fixincludes_4.0.0-12_powerpc.deb to pool/main/g/gcc-4.0/fixincludes_4.0.0-12_powerpc.deb g++-4.0_4.0.0-12_powerpc.deb

Processing of gcc-4.0_4.0.0ds2-12_powerpc.changes

2005-07-06 Thread Archive Administrator
gcc-4.0_4.0.0ds2-12_powerpc.changes uploaded successfully to localhost along with the files: gcc-4.0-base_4.0.0-12_powerpc.deb libgcc1_4.0.0-12_powerpc.deb cpp-4.0_4.0.0-12_powerpc.deb protoize_4.0.0-12_powerpc.deb fixincludes_4.0.0-12_powerpc.deb libmudflap0_4.0.0-12_powerpc.deb libm

Results for 3.4.5 20050706 (prerelease) (Debian 3.4.4-5) testsuite on i486-linux-gnu

2005-07-06 Thread Matthias Klose
=== # of tests4946 # of expected passes 4939 # of unexpected failures 6 # of unsupported tests1 /home/packages/gcc/3.4/gcc-3.4-3.4.4/build/gcc/xgpc version 20050331, based on gcc-3.4.5 20050706 (prerelease) (Debian 3.4.4-5) === acats tests

Bug#317233: gcc-4.0 regression, possibly powerpc-specific, causes segfault in compiled binary

2005-07-06 Thread Matthias Klose
Roger Leigh writes: > Package: gcc-4.0 > Version: 4.0.0-11 > Severity: normal > > If I compile schroot > > http://ftp.debian.org/debian/pool/main/s/schroot/schroot_0.1.2-1.dsc > http://ftp.debian.org/debian/pool/main/s/schroot/schroot_0.1.2.orig.tar.gz > http://ftp.debian.org/debian/pool/main/s/s

Bug#317233: gcc-4.0 regression, possibly powerpc-specific, causes segfault in compiled binary

2005-07-06 Thread Roger Leigh
Package: gcc-4.0 Version: 4.0.0-11 Severity: normal If I compile schroot http://ftp.debian.org/debian/pool/main/s/schroot/schroot_0.1.2-1.dsc http://ftp.debian.org/debian/pool/main/s/schroot/schroot_0.1.2.orig.tar.gz http://ftp.debian.org/debian/pool/main/s/schroot/schroot_0.1.2-1.diff.gz with g

Bug#317106: acknowledged by developer (Re: Bug#317106: gcc-4.0: gcc should warn or ask before changing /usr/bin/gcc link)

2005-07-06 Thread Arne Anka
nice attitude: "it is so cause we say it is so". On Wed, 06 Jul 2005 14:03:10 +0200, Debian Bug Tracking System <[EMAIL PROTECTED]> wrote: This is an automatic notification regarding your Bug report #317106: gcc-4.0: gcc should warn or ask before changing /usr/bin/gcc link, which was file

Bug#316141: marked as done (gcc-snapshot: FTBFS on amd64: Can't find 32 bit libc.)

2005-07-06 Thread Debian Bug Tracking System
brary v3 (shared library subset kit) treelang-3.4 - The GNU Treelang compiler Closes: 290102 315751 316141 Changes: gcc-3.4 (3.4.4-5) unstable; urgency=low . * Updated to gcc-3.4 CVS 20050706. * amd64: Fix 32/libgcc symlinks to point to /usr/lib32, instead of /lib32. Closes: #315751,

Bug#290102: marked as done ([fixed in 4.0] Please recompile with MXUNIT in fio.h increased to >= 1000)

2005-07-06 Thread Debian Bug Tracking System
NU Standard C++ Library v3 (development files) libstdc++6-doc - The GNU Standard C++ Library v3 (documentation files) libstdc++6-pic - The GNU Standard C++ Library v3 (shared library subset kit) treelang-3.4 - The GNU Treelang compiler Closes: 290102 315751 316141 Changes: gcc-3.4 (3.4.4-5) uns

Bug#315751: marked as done (gcc-3.4 can't create ia32 binaries on amd64 anymore.)

2005-07-06 Thread Debian Bug Tracking System
) libstdc++6-dev - The GNU Standard C++ Library v3 (development files) libstdc++6-doc - The GNU Standard C++ Library v3 (documentation files) libstdc++6-pic - The GNU Standard C++ Library v3 (shared library subset kit) treelang-3.4 - The GNU Treelang compiler Closes: 290102 315751 316141 Changes:

gcc-3.4_3.4.4-5_i386.changes ACCEPTED

2005-07-06 Thread Debian Installer
Accepted: cpp-3.4-doc_3.4.4-5_all.deb to pool/main/g/gcc-3.4/cpp-3.4-doc_3.4.4-5_all.deb cpp-3.4_3.4.4-5_i386.deb to pool/main/g/gcc-3.4/cpp-3.4_3.4.4-5_i386.deb g++-3.4_3.4.4-5_i386.deb to pool/main/g/gcc-3.4/g++-3.4_3.4.4-5_i386.deb g77-3.4-doc_3.4.4-5_all.deb to pool/main/g/gcc-3.4/g77-

Processing of gcc-3.4_3.4.4-5_i386.changes

2005-07-06 Thread Archive Administrator
gcc-3.4_3.4.4-5_i386.changes uploaded successfully to localhost along with the files: gcc-3.4_3.4.4-5.dsc gcc-3.4_3.4.4-5.diff.gz cpp-3.4-doc_3.4.4-5_all.deb libgcj5-common_3.4.4-5_all.deb libstdc++6-doc_3.4.4-5_all.deb g77-3.4-doc_3.4.4-5_all.deb gnat-3.4-doc_3.4.4-5_all.deb gpc-2.

Re: Weird assembler messages with GCC 4.0

2005-07-06 Thread Peter Eisentraut
Matthias Klose wrote: > please can you recheck with binutils 2.16 from experimental, That one works. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#317106: marked as done (gcc-4.0: gcc should warn or ask before changing /usr/bin/gcc link)

2005-07-06 Thread Debian Bug Tracking System
Your message dated Wed, 6 Jul 2005 13:52:00 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#317106: gcc-4.0: gcc should warn or ask before changing /usr/bin/gcc link has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt w

Bug#317106: gcc-4.0: gcc should warn or ask before changing /usr/bin/gcc link

2005-07-06 Thread Arne Anka
Package: gcc-4.0 Version: 4.0.0-12 Severity: normal gcc should warn or, better, ask before changing the target of the link /usr/bin/gcc. i lost a half day of work just because /usr/bin/gcc since the update today in the morning points to gcc-4.0 instead of 3.3 which broke my library i had to compi

Processed: Facilitate upgrade

2005-07-06 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: > tags 193787 + sarge etch sid Bug#193787: GCC documentation is non-free Tags were: sarge-ignore Tags added: sarge, etch, sid > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (adminis

Bug#265318: marked as done (gcc-3.4: Doesn't provide a /usr/bin/cc alternative)

2005-07-06 Thread Debian Bug Tracking System
Your message dated Wed, 6 Jul 2005 10:27:24 +0200 with message-id <[EMAIL PROTECTED]> and subject line gcc symlink will not be managed by alternatives 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