On Wed, 16 Jun 2010, Matthias Klose wrote: > - multiarch shouldn't be disabled > - the selection which multilibs to build should be done by patching > gcc/config/m68k/*
Hrm. He didn’t really answer my questions about the c++ symbols problem, but this would help us further along at least. Does anyone have an idea about the symbols thing? • LP bug: https://bugs.launchpad.net/ubuntu/+source/gcc-4.4/+bug/514579 • build log: http://launchpadlibrarian.net/44949657/gcc44m68k.log.gz (338K gzip’d, look at the end) • Thread: http://lists.debian.org/debian-68k/2010/04/msg00025.html What multiarch targets do we want to build? I can see use for m68040, dunno about m68060, don’t think mcpu32 or mfidoa. What about Coldfire – is that a gcc-4.5 thing (I’m strictly concentrating on gcc-4{3,4} with libc-2.7 at the moment)? Does anyone have an idea about the c++ symbols thing? bye, //mirabilos -- «MyISAM tables -will- get corrupted eventually. This is a fact of life. » “mysql is about as much database as ms access” – “MSSQL at least descends from a database” “it's a rebranded SyBase” “MySQL however was born from a flatfile and went downhill from there” – “at least jetDB doesn’t claim to be a database” (#nosec) ‣‣‣ Please let MySQL and MariaDB finally die! -- To UNSUBSCRIBE, email to debian-68k-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/alpine.deb.2.00.1006171037110.7...@tglase.bonn.tarent.de
