Differences between revisions 24 and 171 (spanning 147 versions)
Revision 24 as of 2005-11-07 07:41:07
Size: 2635
Editor: ?cts
Comment:
Revision 171 as of 2018-02-15 23:36:57
Size: 5310
Editor: PaulWise
Comment: correct gcc usertag
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
= linux-2.6 =
 * mac support, especially adb (can't d-i without it)
 * atari is missing support for framebuffer, keyboard, mouse, and serial, plus user space is broken (init dies when starting).
## page was renamed from DebianM68kPorting
#language en
This page tracks current issues with the [[M68k|m68k]] port. User support and buildd admins are at debian-68k@lists.debian.org.
Line 5: Line 5:
= linux-2.4 =
 * Atari and Mac SCC serial drivers missing
 * Atari ST-RAM swap code broken
{{{#!wiki debian
[[http://www.debian.org/ports/m68k/]] - Debian M68k official port page.
}}}
Line 9: Line 9:
= gcc-4.0 =
 * bug triage: which m68k bugs have been fixed and should be closed, which still fail with the latest sid compiler and/or gcc-snapshot http://bugs.debian.org/cgi-bin/pkgreport.cgi?src=gcc-4.0
 * bug fixing
 * debian bug #323686/pr 21123 cp_expr_size ICE (4.0.2-2): many packages including: kxmleditor_1.1.4-2, aleph_0.9.0-2.1, superkaramba_0.36-2, ksubtile_1.1-1
 * more to list [20051011] at least: wordtrans, texmacs, qdbm, kst, kile, kbear, ecos, celestia
 * debian bug #333536, gcc-4.0 (4.0.2-2) ICE in instantiate_virtual_regs_lossage: plptools_0.14-1, rsplib_1.0.0-1, ntop_3:3.2-1, cl-sql_3.3.3-1
 * debian bug #323016, gcc-4.0 (4.0.2-2) unable to find a register to spill in class 'ADDR_REGS': ruby1.8_1.8.3-2, tin 1.7.10+20050727, sharutils? -- workaround -01, fixed in 4.1?
 * debian bug #270340/pr 18592 ICE: output_operand: invalid expression as operand: openmsx_0.5.2-4.
= Other Places =
Line 18: Line 11:
= binutils =
 * sid version is broken: http://bugs.debian.org/327780
 * James Troup said there were m68k-specific patches added and they would be a good place to start.
 * Wouter is hot on the trail <http://www.grep.be/blog/en/computer/debian/m68k/327780>.
 * [[M68k/Meetings/Kiel2008]]
 * [[m68kLennyReleaseRecertification]]
 * [[m68kEtchReleaseRecertification]]
 * [[http://release.debian.org/etch_arch_qualify.html|arch status]]
 * [[DebianInstaller/M68k]]
 * [[M68k/Gcc]]
 * [[M68k/Kernel]]
 * [[M68k/Testing]]
 * [[Aranym]] - ''Atari Running on Any Machine'' virtual machine.
  * [[Aranym/Quick]] – Just let me do it!
  * [[M68k/Cowbuilder]] – Quickly build packages in a clean chroot, even in parallel.
 * [[http://edos.debian.net/edos-debcheck/m68k.php|m68k sid uninstallable]]
Line 23: Line 24:
= xargs (dh_fixperms) =
 * Looks something like
= Here =
 * [[#etch|etch status]]
 * [[#testing|testing status]]
 * [[#usertags|usertags]]
 * [[#rcusertags|RC usertags]]
 * [[#bugs|bugs that need work]]
 * [[#binnmu|binNMU instructions]]
Line 26: Line 32:
{{{> > dh_fixperms
> > chown: cannot access
> > `dedebian/libcommoncpp2-dev/usr/include/cc++2/cc++/common.h': No such file
> > or directory chown: cannot access `TERM=unknown': No such file or directory
> > dh_fixperms: command returned error code}}}
 * The offending command in dh_fixperms is {{{find debian/caudium -print0 2>/dev/null | xargs -0r chown --no-dereference 0:0}}}, with xargs being the culprit
 * Packages known to fail: libcommoncpp2_1.3.19-1, digikamimageplugins_0.7.4-4, drscheme_1:209-8, caudium_2:1.4.7-5, libclass-methodmaker-perl_2.07-2, mozilla_2:1.7.11-1, openssl097_0.9.7g-4, ncurses_5.5-1, sympa_4.1.5-7, pike7.4_7.4.325-2, mpqc_2.2.3-2
 * Workaround: build under kernel 2.4 or better.
Line 35: Line 33:
= Buildd Status = <<Anchor(etch)>>
= Etch-m68k Status =

 * m68k didn't release with debian stable, but rather has it's own semi-supported, semi-released distribution called etch-m68k.
 * A wanna-build for security or proposed-updates type support for etch-m68k has been created, but the autobuilders are currently focused on catching up with unstable distribution. Once m68k is caught up with unstable, cronos and diablos at nemesisnetworks.com are scheduled to begin building both.
 * The good news is that everything works, and we have an upgrade path for the future.

= Testing Links =
 * [[http://buildd.debian.org/status/architecture.php?a=m68k|status]] towards those goals.
Line 37: Line 43:
 * http://buildd.org/
 * Being ignored for testing: http://lists.debian.org/debian-release/2005/10/msg00079.html
 * Looks like 17 left in needs-build, yeah!
 * We need to revisit the 135 failed and cleanup the toolchain bugs.
 * http://buildd.net/
 * udeb [[https://d-i.debian.org/testing-summary.html|testing summary]]
 * udeb [[http://ftp-master.debian.org/~jeroen/d-i.out|consistency check]]
Line 42: Line 47:
= Other Stuff =
 * DebianInstallerM68kTodo
 * InitrdReplacementOptions
 * klibc needs porting see bug #334917

<<Anchor(usertags)>>
= m68k usertags =

 * If you find a bug not listed [[http://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=m68k;users=debian-68k@lists.debian.org;pri0=tag:help,moreinfo,needs-help,needs-port,pending,upstream,patch,gcc-4.0,toolchain|here]], please usertag it or drop us a message.
 * See [[bugs.debian.org/usertags]] for more info about usertags.
 * user debian-68k@lists.debian.org
 * usertag m68k - all m68k-specific issues [[http://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=m68k;users=debian-68k@lists.debian.org|bts]]
 * usertag toolchain - toolchain-related bug, revisit on rev [[http://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=toolchain;users=debian-68k@lists.debian.org|bts]]
 * usertag gcc-4.0 - gcc-4.0-specific problems [[http://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=gcc-4.0;users=debian-68k@lists.debian.org|bts]]
 * usertag needs-port - needs porting work [[http://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=needs-port;users=debian-68k@lists.debian.org|bts]]
 * usertag needs-help - maintainer has requested help
 * usertag pending - patch/solution accepted
 * An email might look like the following:
 {{{
To: control@bugs.debian.org
Subject: m68k usertags

user debian-68k@lists.debian.org
usertag bugnum + m68k
thanks
 }}}


<<Anchor(rcusertags)>>
= m68k rc usertags =

 * user debian-release@lists.debian.org
 * usertag rc-m68k
 * [[http://bugs.debian.org/cgi-bin/pkgreport.cgi?which=tag&users=debian-release@lists.debian.org&tag=rc-m68k|rc-m68k]]
 * all [[http://bugs.debian.org/cgi-bin/pkgreport.cgi?which=tag&users=debian-release@lists.debian.org&tag=rc-arm,rc-m68k,rc-s390,rc-sparc&nam0=Status&pri0=pending:pending,forwarded,pending-fixed,fixed,done&ttl0=Outstanding,Forwarded,Pending%20Upload,Fixed%20in%20NMU,Resolved&nam1=Architecture&pri1=tag:rc-arm,rc-m68k,rc-s390,rc-sparc&ttl1=arm,m68k,s390,sparc&ord1=0,1,2,3|scc]] archs


<<Anchor(bugs)>>
= Bugs =

 * cleanup toolchain.
 * [[http://people.debian.org/~smarenka/m68kbugs/reports/failed-m68konly.html|buildd notes]]

== time-stamp skew ==

 * A missing automake build-dep may instead be time-stamp skew.
 * Search for skew in /usr/share/doc/autotools-dev/README.Debian.gz


<<Anchor(binnmu)>>
= binNMU notes =

 * example to register dpkg_1.13.11 for a dpkg_1.13.11+b1 binNMU:
{{{wanna-build -b m68k/build-db -d unstable -m "Rebuild with g++-4.0 for C++ +transition." --binNMU=1 dpkg_1.13.11}}}
  * --binNMU=2 for second binNMU.

 * example to deregister any pending binNMU and return to Installed state:
{{{wanna-build -b m68k/build-db -d unstable --binNMU=0 dpkg_1.13.11}}}

= Build Priority Notes =

 * example usage to set one-time higher build-priority
{{{wanna-build -b i386/build-db -d unstable --build-priority=1 xorg-x11_6.8.2.dfsg.1-7}}}

 * example usage to set one-time lower build-priority
{{{wanna-build -b i386/build-db -d unstable --build-priority=-1 xorg-x11_6.8.2.dfsg.1-7}}}

 * For permanent build priorities, use --perm-build-priority instead of --build-priority


= Not-For-Us Notes =

 * to remove something from the not-for-us list, use --forget.
 * to move it from n-f-u to nb, use --forget, -o --take, --give-back.
 * apparently you can also just do wb -n again (it toggles)

----
## This page is referenced from http://www.debian.org/ports/m68k/
CategoryPermalink
CategoryPorts

This page tracks current issues with the m68k port. User support and buildd admins are at debian-68k@lists.debian.org.

http://www.debian.org/ports/m68k/ - Debian M68k official port page.

Other Places

Here

Etch-m68k Status

  • m68k didn't release with debian stable, but rather has it's own semi-supported, semi-released distribution called etch-m68k.
  • A wanna-build for security or proposed-updates type support for etch-m68k has been created, but the autobuilders are currently focused on catching up with unstable distribution. Once m68k is caught up with unstable, cronos and diablos at nemesisnetworks.com are scheduled to begin building both.
  • The good news is that everything works, and we have an upgrade path for the future.

Testing Links

m68k usertags

  • If you find a bug not listed here, please usertag it or drop us a message.

  • See bugs.debian.org/usertags for more info about usertags.

  • user debian-68k@lists.debian.org

  • usertag m68k - all m68k-specific issues bts

  • usertag toolchain - toolchain-related bug, revisit on rev bts

  • usertag gcc-4.0 - gcc-4.0-specific problems bts

  • usertag needs-port - needs porting work bts

  • usertag needs-help - maintainer has requested help
  • usertag pending - patch/solution accepted
  • An email might look like the following:
    To: control@bugs.debian.org
    Subject: m68k usertags
    
    user debian-68k@lists.debian.org
    usertag bugnum + m68k
    thanks

m68k rc usertags

Bugs

time-stamp skew

  • A missing automake build-dep may instead be time-stamp skew.
  • Search for skew in /usr/share/doc/autotools-dev/README.Debian.gz

binNMU notes

  • example to register dpkg_1.13.11 for a dpkg_1.13.11+b1 binNMU:

wanna-build -b m68k/build-db -d unstable -m "Rebuild with g++-4.0 for C++ +transition." --binNMU=1 dpkg_1.13.11

  • --binNMU=2 for second binNMU.
  • example to deregister any pending binNMU and return to Installed state:

wanna-build -b m68k/build-db -d unstable --binNMU=0 dpkg_1.13.11

Build Priority Notes

  • example usage to set one-time higher build-priority

wanna-build -b i386/build-db -d unstable --build-priority=1 xorg-x11_6.8.2.dfsg.1-7

  • example usage to set one-time lower build-priority

wanna-build -b i386/build-db -d unstable --build-priority=-1 xorg-x11_6.8.2.dfsg.1-7

  • For permanent build priorities, use --perm-build-priority instead of --build-priority

Not-For-Us Notes

  • to remove something from the not-for-us list, use --forget.
  • to move it from n-f-u to nb, use --forget, -o --take, --give-back.
  • apparently you can also just do wb -n again (it toggles)


CategoryPermalink CategoryPorts