Results for 4.1.3 20070601 (prerelease) (Debian 4.1.2-11) testsuite on powerpc-unknown-linux-gnu

LAST_UPDATED: Fri Jun 1 21:53:34 UTC 2007 (revision 125268) Native configuration is powerpc-unknown-linux-gnu === g++ tests === Running target unix XPASS: g++.dg/tree-ssa/pr14814.C scan-tree-dump-times &this 0 === g++ Summary for unix === # of expected passes

Bug#427278: gcc-4.2-base: should it better be arch: all?

Package: gcc-4.2-base Version: 4.2-20070528-1 Severity: normal When I look at the content of gcc-4.2-base I wonder if it should better be arch: all instead of arch: any. Are there reasons for arch: any? I'm porting to a new architecture and for me it would be useful to have it arch: all, beca

Processed: (pas de sujet)

Processing commands for [EMAIL PROTECTED]: > owner 403460 Arthur Loiret <[EMAIL PROTECTED]> Bug#403460: ITP: gdc -- D programming language for GCC Owner changed from Suresh Rajashekara <[EMAIL PROTECTED]> to Arthur Loiret <[EMAIL PROTECTED]>. > owner 312367 Arthur Loiret <[EMAIL PROTECTED]> Bug#

Re: Bug#427185: zlib - FTBFS: cannot stat `build-tree/zlib-1.2.3/libz.so.1.2.3': No such file or directory

reassign 427185 gcc-4.1 found 427185 4.1.2-11 notfound 427185 1:1.2.3-15 retitle 427185 Warning output when linking 64 bit objects on i386 thanks The enclosed FTBFS in the 64 bit zlib on i386 appears to be a toolchain issue, though I may have assigned it to the wrong package. The issue is that li

Processed: Re: Bug#427185: zlib - FTBFS: cannot stat `build-tree/zlib-1.2.3/libz.so.1.2.3': No such file or directory

Processing commands for [EMAIL PROTECTED]: > reassign 427185 gcc-4.1 Bug#427185: zlib - FTBFS: cannot stat `build-tree/zlib-1.2.3/libz.so.1.2.3': No such file or directory Bug reassigned from package `zlib' to `gcc-4.1'. > found 427185 4.1.2-11 Bug#427185: zlib - FTBFS: cannot stat `build-tree/z