- the compiler testsuites don't show regressions compared to the current
version in hardy. checked in amd64, i386, lpia.
some packages were built using this compiler in my personal PPA (doko); some things fail, but are unrelated to the gcc-4.2 update (amd64 and i386):
- apache2; built, doesn't have a testsuite which is run during the build
- glib2.0; the testsuite doesn't show regressions.
- mysql-dfsg-5.0: no regressions in the testsuite.
- perl: one test fails in the testsuite (hostname lookup), although it succeeds
with a local build. suspecting a setup problem with the buildd.
- php5: one regression (IPv6 Loopback test [ext/sockets/tests/ipv6loop.phpt]),
succeeds with a local build, suspecting a setup problem with the buildd.
- postgresql-8.3: no regressions on amd64, on i386 the testsuite is not run.
- pygtk2.0: build fails on amd64, seen as well with the current gcc version in hardy.
no regressions on i386.
packages are prepared in the ubuntu-toolchain PPA
- the compiler testsuites don't show regressions compared to the current
version in hardy. checked in amd64, i386, lpia.
some packages were built using this compiler in my personal PPA (doko); some things fail, but are unrelated to the gcc-4.2 update (amd64 and i386):
- apache2; built, doesn't have a testsuite which is run during the build
- glib2.0; the testsuite doesn't show regressions.
- mysql-dfsg-5.0: no regressions in the testsuite.
- perl: one test fails in the testsuite (hostname lookup), although it succeeds
with a local build. suspecting a setup problem with the buildd.
- php5: one regression (IPv6 Loopback test [ext/sockets/ tests/ipv6loop. phpt]),
succeeds with a local build, suspecting a setup problem with the buildd.
- postgresql-8.3: no regressions on amd64, on i386 the testsuite is not run.
- pygtk2.0: build fails on amd64, seen as well with the current gcc version in hardy.
no regressions on i386.
- python2.5: no regressions in the testsuite.
- glibc: no regressions in the testsuite