Brian Morris dixit: >I noticed the other day that a new dependency (MPC) from upstream for gcc4.5 > >http://gcc.gnu.org/gcc-4.5/changes.html > >is failing to build on 68k, >see m68k at the bottom of this page, says not since gcc 4.3.
While I can probably take care of compiling gcc-4.5 and its dependencies, we “just” got gcc-4.4 in a pretty good shape, plus it’s used by the kernel, whereas gcc-4.5 is another burden, and $someone would need to check whether the fixes we had added to 4.4 are already in 4.5 (either upstream or Debian) and add them if they aren’t… not impossible, but I don’t know if it’s wise, at the moment (not long-term). Priority is to get the kernel from unstable patched, working and usable at the moment, since the toolchain works now. (Thanks Matthias for accepting the binutils and gcc-4.4 patches!) Oh, and, of course, to get an actual buildd running… bye, //mirabilos -- Solange man keine schmutzigen Tricks macht, und ich meine *wirklich* schmutzige Tricks, wie bei einer doppelt verketteten Liste beide Pointer XORen und in nur einem Word speichern, funktioniert Boehm ganz hervorragend. -- Andreas Bogk über boehm-gc in d.a.s.r -- To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/pine.bsm.4.64l.1103021931310.10...@herc.mirbsd.org
