Differences between revisions 6 and 7
Revision 6 as of 2011-05-06 19:46:39
Size: 1923
Revision 7 as of 2011-07-15 22:20:20
Size: 1798
Deletions are marked like this. Additions are marked like this.
Line 13: Line 13:
== gcc-4.1 ==

Not in sid, but probably works. No TLS support.

== gcc-4.3 ==

Both -fomit-frame-pointer and -foptimize-sibling-calls (default) produce broken code. No TLS support. Removed from sid.
Line 23: Line 15:
Seems to work pretty well. Has TLS backport. Works, has TLS backport.
Line 31: Line 23:
Not ported. Ported; not tested much yet. gcj-4.6 FTBFSes.
Line 42: Line 34:

== rsyslog ==

rsyslog seems broken, but sysklogd works for me.

This page attempts to track the current issues of the Debian/m68k Linux port. Mailing list is at debian-68k@lists.debian.org and more information can be found in this Wiki under M68k and M68k/Porting.


Get an Aranym/Quick image (sid from ca. 2008/2009 with libc 2.7) and put an updated M68k/Cowbuilder chroot on it. Stephen Marenka’s sid image is reported to work as well. The status of everything else is unknown, however, you can probably install the etch-m68k snapshot. But if you wanted to dig out that you wouldn’t be here, right?


Some packages are in debian-ports.org unreleased, not in unstable, because they need m68k-local patches. For some, this is because maintainers keep unstable frozen during the squeeze/testing freeze in order to be able to upload fixes via unstable. For some, this is a collection of patches or workarounds that are not, or will not be, included in the proper Debian packages. Once installed, however, it’s fine to work from unstable only (unless you want to hack the packages from unreleased).



Works, has TLS backport.


Not ported. Has TLS upstream. Will not be ported, we’ll be switching from gcc-4.4 directly to gcc-4.6 when the time is right; wheezy will not be released with gcc-4.5 anyway.


Ported; not tested much yet. gcj-4.6 FTBFSes.

core system


All outstanding issues are apparently fixed now.


Patches submitted; may or may not be enough (will be revisited).


rsyslog seems broken, but sysklogd works for me.