Differences between revisions 1 and 141 (spanning 140 versions)
Revision 1 as of 2005-10-11 15:37:37
Size: 901
Editor: ?smarenka
Comment:
Revision 141 as of 2007-06-01 21:59:49
Size: 5627
Editor: ?smarenka
Comment:
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 framebuffer
This page tracks current issues with the [http://www.us.debian.org/ports/m68k/ m68k] port. User support and buildd admins are at debian-68k@lists.debian.org.
Line 5: Line 3:
= linux-2.4 =
 * Atari and Mac SCC serial drivers missing
 * Atari ST-RAM swap code broken
= Other Places =
Line 9: Line 5:
= gcc-4.0 =
 * start listing bugs
 * ["m68kEtchReleaseRecertification"]
 * [http://release.debian.org/etch_arch_qualify.html arch status]
 * DebianInstaller/M68kTodo
 * DebianM68kGcc
 * DebianM68kKernel
 
= Here =
 * [#etch etch status]
 * [#testing testing status]
 * [#usertags usertags]
 * [#rcusertags RC usertags]
 * [#bugs bugs that need work]
 * [#binnmu binNMU instructions]
Line 12: Line 19:
= 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.
Line 16: Line 20:
= xargs (dh_fixperms) = [[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.
 * Right now there is no security or proposed-updates type support for etch-m68k, but it is in the works.
 * The good news is it works fine.

[[Anchor(testing)]]
= Testing Status =

 * m68k isn't even in lenny at the moment since the RMs felt the toolchain needs work.
 * glibc needs TLS support.
 * The m68k-specific patches for gcc-4.2 cleaned up.
 * Submit gcc-snapshot test results.

= Testing Links =
 * [http://buildd.debian.org/~jeroen/status/architecture.php?a=m68k status] towards those goals.
 * http://buildd.debian.org/
 * http://buildd.net/
 * udeb [http://merkel.debian.org/~joeyh/d-i/testing-summary.html testing summary]
 * udeb [http://ftp-master.debian.org/~jeroen/d-i.out consistency check]


[[Anchor(usertags)]]
= m68k usertags =

 * If you find a bug not listed [http://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=m68k;users=m68k-build@nocrew.org;pri0=tag:help,moreinfo,needs-help,needs-port,pending,upstream,patch,gcc-40,toolchain here], please usertag it or drop us a message.
 * See ["bugs.debian.org/usertags"] for more info about usertags.
 * user m68k-build@nocrew.org
 * usertag m68k - all m68k-specific issues [http://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=m68k;users=m68k-build@nocrew.org bts]
 * usertag toolchain - toolchain-related bug, revisit on rev [http://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=toolchain;users=m68k-build@nocrew.org bts]
 * usertag gcc-40 - gcc-4.0-specific problems [http://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=gcc-40;users=m68k-build@nocrew.org bts]
 * usertag needs-port - needs porting work [http://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=needs-port;users=m68k-build@nocrew.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 m68k-build@nocrew.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.

== xargs (dh_fixperms) ==

 * update 2006-07-31: fails on 2.2.x kernels, requeue on buildd with newer kernel.
 * We've routed around this by upgrading all our buildds.
Line 24: Line 91:
 * The offending command is {{{find debian/caudium -print0 2>/dev/null | xargs -0r chown --no-dereference 0:0}}}, with xargs being the problem
Line 26: Line 92:
= Other Stuff =
 * DebianInstallerM68kTodo
 * 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
 * Workaround: build under kernel 2.4 or better
 * debian bug #336461 (findutils/xargs) seems suspiciously similar
 * similar problem?
     * packagesearch_2.0.5: Built fine on aahz (with 2.6.14), but failed on tanda (with 2.2.25):
        strip --remove-section=.comment --remove-section=.note debian/packagesearch/usr/bin/packagesearch
        strip: Unable to recognise the format of the input file `debian/packagesearch/usr/bin/packagesearch'
        dh_strip: command returned error code 256


== 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.

This page tracks current issues with the [http://www.us.debian.org/ports/m68k/ m68k] port. User support and buildd admins are at debian-68k@lists.debian.org.

Other Places

Here

  • [#etch etch status]
  • [#testing testing status]
  • [#usertags usertags]
  • [#rcusertags RC usertags]
  • [#bugs bugs that need work]
  • [#binnmu binNMU instructions]

?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.
  • Right now there is no security or proposed-updates type support for etch-m68k, but it is in the works.
  • The good news is it works fine.

?Anchor(testing)

Testing Status

  • m68k isn't even in lenny at the moment since the RMs felt the toolchain needs work.
  • glibc needs TLS support.
  • The m68k-specific patches for gcc-4.2 cleaned up.
  • Submit gcc-snapshot test results.

Testing Links

?Anchor(usertags)

m68k usertags

{{{To: control@bugs.debian.org Subject: m68k usertags

user m68k-build@nocrew.org usertag bugnum + m68k thanks }}}

?Anchor(rcusertags)

m68k rc usertags

?Anchor(bugs)

Bugs

  • cleanup toolchain.

xargs (dh_fixperms)

  • update 2006-07-31: fails on 2.2.x kernels, requeue on buildd with newer kernel.
  • We've routed around this by upgrading all our buildds.
  • Looks something like

{{{> > 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

  • Workaround: build under kernel 2.4 or better
  • debian bug #336461 (findutils/xargs) seems suspiciously similar
  • similar problem?
    • packagesearch_2.0.5: Built fine on aahz (with 2.6.14), but failed on tanda (with 2.2.25):
      • strip --remove-section=.comment --remove-section=.note debian/packagesearch/usr/bin/packagesearch strip: Unable to recognise the format of the input file `debian/packagesearch/usr/bin/packagesearch' dh_strip: command returned error code 256

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.