| |||||||||||||
Stable kernel 3.2.35Stable kernel 3.2.35Posted Dec 13, 2012 14:11 UTC (Thu) by mirabilos (subscriber, #84359)Parent article: Stable kernel 3.2.35
Yay, finally KDE 4 works on Debian/m68k with this kernel!
(There was a fix related to threads and signals.)
(Log in to post comments)
Stable kernel 3.2.35 Posted Dec 13, 2012 17:57 UTC (Thu) by mathstuf (subscriber, #69389) [Link]
Two things. First, you mentioned elsewhere[1] that you dislike KDE4, what's the excitement here from then? Second, I thought GCC dropped 68k support back around the 4.2 times. Is it really using an old GCC, some backport, or something else? Am I missing some humor somewhere?
Stable kernel 3.2.35 Posted Dec 13, 2012 18:43 UTC (Thu) by mirabilos (subscriber, #84359) [Link]
I personally dislike KDE 4 as a GUI, but with my Debian hat on, I’m building official Debian/m68k packages. That they run merely shows that all the recent bugfixes (including the Linux kernel one that went into 3.2.35, thanks again bwh for all the accomodating) were good for something.
I’m building with Debian-Ports¹ gcc-4.6, which is just much more tested and somewhat bugfixed than Debian gcc-4.7 (and Debian gcc-4.4 which works well too though), but all three are available. GCC upstream is pretty active, although usually on the Coldfire side of m68k from Mikael Petterson, and Andreas Schwab is dealing with eglibc in addition to the toolchain and usually our rescuer.
① Debian-Ports because it’s a build containing patches not in unstable yet, and unlikely to go in before wheezy’s out: a backport of gcc-trunk (or 4.7)’s atomic builtins – used by Qt4 – and a port to FreeMiNT, among others.
Stable kernel 3.2.35 Posted Dec 13, 2012 18:48 UTC (Thu) by jrn (subscriber, #64214) [Link]
> Second, I thought GCC dropped 68k support back around the 4.2 times.
News to me.
Stable kernel 3.2.35 Posted Dec 13, 2012 19:18 UTC (Thu) by mathstuf (subscriber, #69389) [Link]
I remember Kevin Kofler mentioning that he had to keep backporting the 68k support to keep TIGCC working. I haven't used TIGCC in a few years, so if I'm mistaken, it's purely from out-of-date information.
Stable kernel 3.2.35 Posted Dec 13, 2012 19:41 UTC (Thu) by mirabilos (subscriber, #84359) [Link]
I have no idea what TIGCC is… but maybe it needs m68k-elf (bare, not m68k-linux-gnu) or a.out or something?
Note we *do* add FreeMiNT (m68k-atari-mint, with vendor) target support in order to be able to compile the bootloaders, but the GNU/Linux (and µClinux) support for M68000 and Coldfire is upstream and active.
Stable kernel 3.2.35 Posted Dec 13, 2012 20:15 UTC (Thu) by mathstuf (subscriber, #69389) [Link]
TIGCC is the project used to compile C code for the TI 68k calculators. I don't know what triplet was used.
Stable kernel 3.2.35 Posted Dec 13, 2012 20:27 UTC (Thu) by mirabilos (subscriber, #84359) [Link]
Hm, well. gcc-4.4 obsoleted generic a.out for m68k: http://gcc.gnu.org/gcc-4.4/changes.html
But other than that, I can’t find anything. *shrug*
Stable kernel 3.2.35 Posted Dec 13, 2012 21:11 UTC (Thu) by mirabilos (subscriber, #84359) [Link]
The patch is here: http://tigcc-linux.cvs.sourceforge.net/viewvc/tigcc-linux...
It’s not very good:
It uses the m68k-*-coff* vendor-triplet which isn’t removed.
|
|||||||||||||