I was going to reassign this back to gcc-3.2 but I see the control message must have never gone through...
On Thu, Jan 16, 2003 at 10:33:20PM +0100, Matthias Klose wrote: > reassign 177036 module-init-tools > thanks > > > Debian Bug Tracking System writes: > > Processing commands for [EMAIL PROTECTED]: > > > > > reassign 177036 gcc-3.2 > > Bug#177036: module-init-tools_0.9.8-1(m68k/unstable/poseidon): FTBFS on m68k > > Bug reassigned from package `module-init-tools' to `gcc-3.2'. > > > > > retitle 177036 Statically linking executable fails (no crtbeginT.o on > > > m68k) > > Bug#177036: module-init-tools_0.9.8-1(m68k/unstable/poseidon): FTBFS on m68k > > Changed Bug title. > > please provide the missing information when reassigning the report to > gcc: > > - gcc version used (including the Debian release) > - last gcc version used to sucessfully build m-i-t on m68k > > Then reassign back the report to gcc-3.2. > > Thanks, > > Matthias The two items in the above list are obvious from looking at: http://buildd.debian.org/build.php?arch=&pkg=module-init-tools It worked with gcc 2.95.x on Dec 28, 2002, and failed on gcc 3.2.x on Jan 16, 2003, any more details than that are not given by sbuild, as far as I can tell, so how is a regular maintainer supposed to give you this information??? Perhaps a bug should be filed against sbuild to give more detailed information for situations like this? Chris
