Results for 4.5.1 20100725 (prerelease) (Debian 4.5.0-10) testsuite on i486-pc-linux-gnu

2010-07-26 Thread Matthias Klose
LAST_UPDATED: Obtained from SVN: tags/gcc_4_5_0_release revision 158339 Target: i486-linux-gnu gcc version 4.5.1 20100725 (prerelease) (Debian 4.5.0-10) Native configuration is i486-pc-linux-gnu === g++ tests === Running target unix === g++ Summary for unix ===

Results for 4.5.1 20100725 (prerelease) (Debian 4.5.0-10) testsuite on x86_64-pc-linux-gnu

2010-07-26 Thread Matthias Klose
LAST_UPDATED: Obtained from SVN: tags/gcc_4_5_0_release revision 158339 Target: x86_64-linux-gnu gcc version 4.5.1 20100725 (prerelease) (Debian 4.5.0-10) Native configuration is x86_64-pc-linux-gnu === g++ tests === Running target unix === g++ Summary for unix

[bts-link] source package gcc-4.4

2010-07-26 Thread bts-link-upstream
# # bts-link upstream status pull for source package gcc-4.4 # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user bts-link-upstr...@lists.alioth.debian.org # remote status report for #581571 (http://bugs.debian.org/581571) # * http://gcc.gnu.org/PR44631 # * remote st

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

2010-07-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package gcc-4.4 > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # > user bts-link-upstr...@lists.alioth.debian.org Setting user to bts-link-upstr...@lists.alioth.debian.o

Processed: forwarded gcc reports

2010-07-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 590152 http://gcc.gnu.org/PR45079 Bug #590152 [gcc-4.5] gcc-4.5: ‘c_maybe_const_expr’ not supported by pp_c_expression Set Bug forwarded-to-address to 'http://gcc.gnu.org/PR45079'. > tag 590152 + upstream Bug #590152 [gcc-4.5] gcc-4

Bug#553045: but 4.4.1-1 is to be installed.

2010-07-26 Thread Hector Oron
Hello Matthias, 2010/7/26 Matthias Klose : >> If you lack time I propose myself as GCC co-maintainer to have a look >> to such failures, > > No, I didn't see any contributions yet, even after our talk at last Debconf. >  I do not want to make you a member of the group based on work which might > o