Steve Langasek writes: > Hi Matthias, > > On Sat, May 14, 2005 at 10:52:23PM +0200, Matthias Klose wrote: > Content-Description: message body text > > I'm proposing the following updates for gcc-3.3 for testing: > > > gcc-3.3 (1:3.3.5-13) testing-proposed-updates; urgency=low > > > * Disable running the boehm-gc testsuite on hppa. Hangs the buildd's > > on some builds. > > > Sometimes seen on the buildd's. Conditionally done for hppa, should > > not affect the other architectures. > > > * Don't call dh_shlibdeps on 64bit libraries, fixing FTBFS on sparc, > > which couldn't be observed before (addresses: #307625). > > > > The same fix as done for gcc-3.4. > > Shouldn't both of the above problems go away anyway post-release when the > buildds are updated with (presumably) fixed kernels?
I've seen the former on a current hppa sarge system as well, I cannot comment on the second one. > > * Manually patch all `configure' files for libraries to use > > deplibs_check_method=pass_all unconditionally for all linux > > architectures; > > disable the autoreconf patch. > > > Reviewed by Ryan Murray, applied in the 3.3.6 package. Test builds on > > mips were done by Thiemo Seufer. > > What problem does this fix? The configury get's wrong, if autoconf is installed on the build system. See #310167. Adding a build-conflict on autoconf is an alternative, but I would prefer the patch as submitted. > > * Fix gcc-3.3-hppa64, gij-3.3 and gcj-3.3 postinst, to not ignore errors > > from update-alternatives. > > * Fix gcc-3.3-hppa64, fastjar, gij-3.3 and gcj-3.3 prerm, > > to not ignore errors from update-alternatives. > > > Same fixes as for gcc-3.4. > > Sounds perfectly reasonable. > > > Three upstream changes, which are in gcc-3.3.6. > > > - Fix for http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20670, wrong > > code generation on ia64, patch is local to ia64, fixed in > > 3.3.6, 3.4.4 (not yet fixed in the gcc-3.4 testing version, where it > > should be fixed as well, the shared libgcc is built from gcc-3.4). not needed, because gcc-3.4 is configure --with-system-libunwind > > - Fix for http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19579, wrong > > code generation at -O2 for -march=i686, a regression from 3.3.4, > > 3.3.5, 3.4.0, 3.4.3, fixed in the gcc-3.4 version in testing. checked only that the testcase. > > - Fix for http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20286, an > > ice-on-valid-code, patch is local to ia64, a regression from > > 3.3.5 and 3.3.4. > > "The current PAPI (icl.cs.utk.edu) source code does not compile > > on Debian/testing on IA-64. The current gcc 3.3.5 panics when > > compiling threads.c" > > Are these linked to known problems within Debian packages, or suspected to > affect the buildability of binary packages currently in sarge? An ice-on-valid-code results in an FTBFS, so this should have been detected. Wrong code generation for -march=i686 might effect packages built with this optimization (we do have some), but it's not a "known problem within a Debian package". Known bad code generation is bad enough. Matthias -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]