Differences between revisions 46 and 171 (spanning 125 versions)
Revision 46 as of 2005-11-10 13:47:49
Size: 4123
Editor: ?smarenka
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:
= m68k usertag thoughts = ## 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 3: Line 5:
 * user m68kport
 * tag toolchain: gcc or binutils bug?
 * tag gcc-4.0, gcc-3.4, binutils instead?
 * tag needs-port: needs porting work (e.g., klibc, parted)
{{{#!wiki debian
[[http://www.debian.org/ports/m68k/]] - Debian M68k official port page.
}}}

= Other Places =

 * [[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]]

= Here =
 * [[#etch|etch status]]
 * [[#testing|testing status]]
 * [[#usertags|usertags]]
 * [[#rcusertags|RC usertags]]
 * [[#bugs|bugs that need work]]
 * [[#binnmu|binNMU instructions]]
Line 9: Line 33:
= 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).
 * How to build a cross-compiler for kernel building: http://people.debian.org/~cts/debian-m68k/cross-compile/
<<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.
 * http://buildd.debian.org/
 * 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 15: Line 48:
= linux-2.4 =
 * Atari and Mac SCC serial drivers missing
 * Atari ST-RAM swap code broken
<<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
 }}}
Line 20: Line 71:
= gcc triage =
 * check against latest sid gcc-4.0
 * check against latest sid gcc-3.4
 * bug is listed in debian bts http://bugs.debian.org/cgi-bin/pkgreport.cgi?src=gcc-4.0
 * bug is listed upstream http://gcc.gnu.org/bugzilla/
 * check against gcc-snapshot (if it's more recent)
 * check against gnu compiler (w/o debian patches)
 * update and close old bug reports
<<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
Line 30: Line 80:
= gcc-4.0 bugs = <<Anchor(bugs)>>
= Bugs =
Line 32: Line 83:
 * ICE in cp_expr_size
  * debian #323686 and 323133, gnu pr 21123
  * found in gcc-4.0 4.0.2-2
  * workaround: gcc-3.4, fixed in 4.1? fixed in 4.0.3 according to http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21123
  * pkgs: aleph_0.9.0-2.1, ardour_0.99-3, baghira_0.7a-1, bibletime_1.5.1-1, inkscape_0.42.2+0.43pre1-1, kfolding_1.0.0-rc2-4, klibido_0.2.4.1-1, ksubtile_1.1-1, ktorrent_1.1-1, ktrack_0.3.0-alpha1-6.1
 * cleanup toolchain.
 * [[http://people.debian.org/~smarenka/m68kbugs/reports/failed-m68konly.html|buildd notes]]
Line 38: Line 86:
 * ICE in instantiate_virtual_regs_lossage
  * debian #333536
  * found in gcc-4.0 4.0.2-2
  * pkgs: cl-sql_3.3.3-1, ntop_3:3.2-1, plptools_0.14-1, rsplib_1.0.0-1, squashfs_1:2.2r2-1
== time-stamp skew ==
Line 43: Line 88:
 * ICE: output_operand: invalid expression as operand:
  * debian #270340, gnu pr 18592
  * found in gcc-4.0 4.0.2-2
  * pkgs: gnutls11_1.0.16-14, openmsx_0.5.2-4, zynaddsubfx_2.2.1-2.1

 * segfault
  * found in gcc-4.0 4.0.2-3
  * don't know if all these are related
  * pkgs: asterisk_1:1.0.9.dfsg-5, csound_1:4.23f13-1
  * hmmm: scsitools_0.8-2 failed on crest, but built on vault13 2 days later with the same toolchain?
  * debian #317475 (not verified with 4.0.2-3 yet)
  * python2.2_2.2.3dfsg-4, python2.3_2.3.5-8, python2.4_2.4.1-2, python-imaging_1.1.5-4, pyopengl_2.0.1.09-1.1
  * boost: 321486, segfault, (retry, dep-wait on icu)

 * nmh: ICE reload_cse_simplify_operands
  * found in gcc-4.0 4.0.2-3

 * icu: ICE mem_loc_descriptor
  * found in gcc-4.0 4.0.2-3
 * A missing automake build-dep may instead be time-stamp skew.
 * Search for skew in /usr/share/doc/autotools-dev/README.Debian.gz
Line 64: Line 92:
= gcc-3.4 bugs =
 
  * fftw3: ICE in reload
   * debian #323426, found in gcc-3.4 3.4.4-9
   * retry w/gcc-4.0
<<Anchor(binnmu)>>
= binNMU notes =
Line 70: Line 95:
  * kdemultimedia: ICE verify_initial_elim_offsets
   * found in gcc-3.4 3.4.4-9
   * retry w/gcc-4.0 (1h on kullervo to fail)
 * 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.
Line 74: Line 99:
  * kdebindings: internal error
   * found in gcc-3.4 3.4.4-8
   * retry w/-9 and gcc-4.0 (10h on hobbes to fail)
 * 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
Line 79: Line 113:
= binutils =
 * sid version is broken: http://bugs.debian.org/327780
 * patch supplied in bug report (thanks Wouter and Alan Modra).
= Not-For-Us Notes =
Line 83: Line 115:
 * 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)
Line 84: Line 119:
= xargs (dh_fixperms) =
 * 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
 * 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.

= Buildd Status =
 * http://buildd.debian.org/
 * http://buildd.org/
 * Being ignored for testing: http://lists.debian.org/debian-release/2005/10/msg00079.html
 * We've caught up!
 * We need to revisit the 135 failed and cleanup the toolchain bugs.


= Other Stuff =
 * ["m68kEtchReleaseRecertification"]
 * DebianInstallerM68kTodo
 * InitrdReplacementOptions
 * klibc needs porting see bug #334917
----
## 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