debian-68k  

Messages by Date

• 2026/04/13 Bug#1133678: mold: Please don't build-depend on clang on arches where it's not available John Paul Adrian Glaubitz
• 2026/03/30 Bug#1132270: ffmpeg: Please disable vsynth2-ffvhuff420p12 test on all big-endian targets John Paul Adrian Glaubitz
• 2026/03/06 Bug#1129945: galera-4 FTBFS on hppa, m68k and sh4 due to undefined reference to `boost::program_options Otto Kekäläinen
• 2026/03/02 Re: Preliminary results - was: Re: Question on BIGGEST_ALIGNMENT in GCC on NetBSD/m68k Geert Uytterhoeven
• 2026/02/17 Upstream issue tracker for m68k created John Paul Adrian Glaubitz
• 2026/02/14 Bug#1127874: webkit2gtk: Please update no-must-tail.patch to cover all architectures John Paul Adrian Glaubitz
• 2026/02/13 Re: Bug#1125380: webkit2gtk: Please include patch to disable mustfail property on m68k and sh4 John Paul Adrian Glaubitz
• 2026/02/11 Re: Preliminary results - was: Re: Question on BIGGEST_ALIGNMENT in GCC on NetBSD/m68k Geert Uytterhoeven
• 2026/02/11 Re: Bug#1127603: binutils: Please adjust ignore list for regressions on m68k John Paul Adrian Glaubitz
• 2026/02/10 Bug#1127603: binutils: Please adjust ignore list for regressions on m68k John Paul Adrian Glaubitz
• 2026/02/02 Re: Preliminary results - was: Re: Question on BIGGEST_ALIGNMENT in GCC on NetBSD/m68k Geert Uytterhoeven
• 2026/01/27 Bug#1126521: glibc: FTBFS on m68k with gcc-15 John Paul Adrian Glaubitz
• 2026/01/15 Bug#1125517: libgit2: Consider switching to llhttp again John Paul Adrian Glaubitz
• 2026/01/13 Re: Bug#1066890: rdma-core: don't build docs on minor arches (-DNO_MAN_PAGES=1) Benjamin Drung
• 2026/01/13 Bug#1125380: webkit2gtk: Please include patch to disable mustfail property on m68k and sh4 John Paul Adrian Glaubitz
• 2026/01/12 Bug#1125347: webkit2gtk: Please build with GCC options to avoid OOM issues on 32-bit targets John Paul Adrian Glaubitz
• 2026/01/09 Re: [PATCH 1/2] m68k: Use vDSO for thread pointer access Adhemerval Zanella Netto
• 2026/01/09 Bug#1125101: RM: xpra [armhf i386] -- RoQA; not built since 2023, still depends on pre-t64 libraries Simon McVittie
• 2026/01/09 Re: [PATCH 1/2] m68k: Use vDSO for thread pointer access Florian Weimer
• 2026/01/08 Re: [PATCH 1/2] m68k: Use vDSO for thread pointer access Stefan Reinauer
• 2026/01/08 Re: [PATCH 1/2] m68k: Use vDSO for thread pointer access Stefan Reinauer
• 2026/01/08 Re: [PATCH 0/2] m68k: Add vDSO support for TLS and clock_gettime64 Andreas K. Huettel
• 2026/01/08 Re: [PATCH 1/2] m68k: Use vDSO for thread pointer access Adhemerval Zanella Netto
• 2026/01/08 Re: [PATCH 1/2] m68k: Use vDSO for thread pointer access Florian Weimer
• 2026/01/07 [PATCH 1/2] m68k: Use vDSO for thread pointer access Stefan
• 2026/01/07 [PATCH 0/2] m68k: Add vDSO support for TLS and clock_gettime64 Stefan
• 2026/01/07 [PATCH 2/2] m68k: Enable vDSO clock_gettime64 Stefan
• 2026/01/07 Re: Preliminary results - was: Re: Question on BIGGEST_ALIGNMENT in GCC on NetBSD/m68k Finn Thain
• 2026/01/07 Re: Preliminary results - was: Re: Question on BIGGEST_ALIGNMENT in GCC on NetBSD/m68k Arnd Bergmann
• 2026/01/06 Re: Preliminary results - was: Re: Question on BIGGEST_ALIGNMENT in GCC on NetBSD/m68k John Paul Adrian Glaubitz
• 2026/01/06 Re: Preliminary results - was: Re: Question on BIGGEST_ALIGNMENT in GCC on NetBSD/m68k Geert Uytterhoeven
• 2026/01/06 Re: Preliminary results - was: Re: Question on BIGGEST_ALIGNMENT in GCC on NetBSD/m68k John Paul Adrian Glaubitz
• 2026/01/06 Re: Preliminary results - was: Re: Question on BIGGEST_ALIGNMENT in GCC on NetBSD/m68k Kolbjørn Barmen
• 2026/01/06 Re: Preliminary results - was: Re: Question on BIGGEST_ALIGNMENT in GCC on NetBSD/m68k John Paul Adrian Glaubitz
• 2026/01/01 Re: Bug#1066890: rdma-core: don't build docs on minor arches (-DNO_MAN_PAGES=1) John Paul Adrian Glaubitz
• 2026/01/01 Re: Bug#1066890: rdma-core: don't build docs on minor arches (-DNO_MAN_PAGES=1) John Paul Adrian Glaubitz
• 2025/12/31 Re: qemu-system-sh4eb build has something hinky in the ethernet Rob Landley
• 2025/12/29 Contacto Alejandro Sanchez
• 2025/12/29 Re: Bug#1124228: libavif: Build-depends on libgav1 which build-depends on architecture-is-little-endian John Paul Adrian Glaubitz
• 2025/12/28 Bug#1124228: libavif: Build-depends on libgav1 which build-depends on architecture-is-little-endian John Paul Adrian Glaubitz
• 2025/12/18 Bug#1123577: nmu: mesa_25.2.8-2: +b3 on !amd64 Simon McVittie
• 2025/12/15 Re: gimp 3 FTBFS on big-endian Jeremy Bícha
• 2025/12/14 Re: gimp 3 FTBFS on big-endian Jeremy Bícha
• 2025/12/12 Bug#1122804: RM: r-cran-blme [armel armhf i386 mipsel] -- ROM; Please remove for 32 bit architectures (architecture-is-64-bit was added to Build-Depends) Andreas Tille
• 2025/12/11 Re: Bug#1122336: libreoffice: Smoketest fails on hppa and powerpc due to missing soffice.sh Rene Engelhard
• 2025/12/11 Re: Bug#1122336: libreoffice: Smoketest fails on hppa and powerpc due to missing soffice.sh Rene Engelhard
• 2025/12/11 Re: Bug#1122336: libreoffice: Smoketest fails on hppa and powerpc due to missing soffice.sh Rene Engelhard
• 2025/12/11 Re: Bug#1122336: libreoffice: Smoketest fails on hppa and powerpc due to missing soffice.sh John Paul Adrian Glaubitz
• 2025/12/11 Re: Bug#1122336: libreoffice: Smoketest fails on hppa and powerpc due to missing soffice.sh Rene Engelhard
• 2025/12/11 Re: Bug#1122336: libreoffice: Smoketest fails on hppa and powerpc due to missing soffice.sh Rene Engelhard
• 2025/12/11 Re: Bug#1122336: libreoffice: Smoketest fails on hppa and powerpc due to missing soffice.sh Rene Engelhard
• 2025/12/11 Re: Bug#1122336: libreoffice: Smoketest fails on hppa and powerpc due to missing soffice.sh John Paul Adrian Glaubitz
• 2025/12/11 Re: Bug#1122336: libreoffice: Smoketest fails on hppa and powerpc due to missing soffice.sh Rene Engelhard
• 2025/12/11 Re: Bug#1122336: libreoffice: Smoketest fails on hppa and powerpc due to missing soffice.sh John Paul Adrian Glaubitz
• 2025/12/10 Bug#1122336: libreoffice: Smoketest fails on hppa and powerpc due to missing soffice.sh John Paul Adrian Glaubitz
• 2025/12/08 Bug#1122205: RM: rhonabwy -- ROM; upstream is no longer maintained and depends on obsolete packages, FTBFS with gnutls 3.8.11 Nicolas Mora
• 2025/12/05 Re: Bug#1121969: python3.14: Please build with -O1 on m68k to workaround interpretor lockups John Paul Adrian Glaubitz
• 2025/12/05 Re: Bug#1121969: python3.14: Please build with -O1 on m68k to workaround interpretor lockups Eero Tamminen
• 2025/12/05 Bug#1121974: python3.13: Please build with -O1 on m68k to workaround interpretor lockups John Paul Adrian Glaubitz
• 2025/12/05 Bug#1121970: RM: r-cran-freetypeharfbuzz [armel armhf i386 mipsel] -- ROM; Please remove for 32 bit architectures (architecture-is-64-bit was added to Build-Depends) Andreas Tille
• 2025/12/05 Bug#1121969: python3.14: Please build with -O1 on m68k to workaround interpretor lockups John Paul Adrian Glaubitz
• 2025/12/04 Re: Architecture baseline for Forky Rob Landley
• 2025/12/03 Re: Bug#1121780: Please revert 3.13.9 version bump to help m68k Jeffrey Walton
• 2025/12/03 Re: Bug#1121780: Please revert 3.13.9 version bump to help m68k John Paul Adrian Glaubitz
• 2025/12/02 Re: Bug#1121780: Please revert 3.13.9 version bump to help m68k John Paul Adrian Glaubitz
• 2025/12/02 Bug#1121780: Please revert 3.13.9 version bump to help m68k Adrian Bunk
• 2025/12/02 OMP fixed in the llvm-21 packaging Matthias Klose
• 2025/11/23 64mb limitation of qemu-system-sh4 board Philippe Mathieu-Daudé
• 2025/11/23 Re: qemu-system-sh4eb build has something hinky in the ethernet Philippe Mathieu-Daudé
• 2025/11/23 Re: 64mb limitation of qemu-system-sh4 board John Paul Adrian Glaubitz
• 2025/11/23 gcc-16, first packaging bits Matthias Klose
• 2025/11/22 Re: internal compiler error while building sqlite3 for m68k Matthias Klose
• 2025/11/20 What does the publishing charged? stephanie M.pigg
• 2025/11/12 Re: Architecture baseline for Forky Lucas Nussbaum
• 2025/11/12 Re: Architecture baseline for Forky Adrian Bunk
• 2025/11/06 Re: Architecture baseline for Forky Holger Levsen
• 2025/11/05 Re: Architecture baseline for Forky Lucas Nussbaum
• 2025/11/05 Re: Hard Rust requirements from May onward Sean Whitton
• 2025/11/05 Re: Bug#1118058: scipy: m68k fails: sparsetools/bsr.h unable to find a register to spill in class ‘ADDR_REGS’ Drew Parsons
• 2025/11/05 Re: Bug#1118058: scipy: m68k fails: sparsetools/bsr.h unable to find a register to spill in class ‘ADDR_REGS’ John Paul Adrian Glaubitz
• 2025/11/05 Bug#1118058: scipy: m68k fails: sparsetools/bsr.h unable to find a register to spill in class ‘ADDR_REGS’ Drew Parsons
• 2025/11/05 Re: Planned obsolescence ? (OpenBSD) Philipp Kern
• 2025/11/04 Re: Planned obsolescence ? (*BSD, Rust) Falco Girgis
• 2025/11/04 Re: Planned obsolescence ? (OpenBSD) John David Anglin
• 2025/11/04 Re: Planned obsolescence ? (*BSD, Rust) Christopher Huhn
• 2025/11/04 Re: Planned obsolescence ? (*BSD, Rust) Dr. Arne Babenhauserheide
• 2025/11/04 Re: Planned obsolescence ? Riccardo Mottola
• 2025/11/04 Re: Planned obsolescence ? (*BSD, Rust) Riccardo Mottola
• 2025/11/04 Re: Planned obsolescence ? Jaromír Cápík
• 2025/11/03 Re: Planned obsolescence ? (*BSD, Rust) David Starner
• 2025/11/03 Re: Planned obsolescence ? (*BSD, Rust) Jan-Daniel Kaplanski
• 2025/11/03 Re: Planned obsolescence ? (*BSD, Rust) David Starner
• 2025/11/02 Re: Planned obsolescence ? (*BSD, Rust) Jan-Daniel Kaplanski
• 2025/11/02 Re: Hard Rust requirements from May onward Jeffrey Walton
• 2025/11/02 Re: Planned obsolescence ? (OpenBSD) Paul Tagliamonte
• 2025/11/02 Re: Planned obsolescence ? (OpenBSD) jbranso
• 2025/11/02 Re: Hard Rust requirements from May onward Joerg Jaspert
• 2025/11/02 Re: Hard Rust requirements from May onward Julian Andres Klode
• 2025/11/02 Re: Hard Rust requirements from May onward Bill Allombert
• 2025/11/02 Re: Hard Rust requirements from May onward Joerg Jaspert
• 2025/10/31 Re: Hard Rust requirements from May onward Nelson H. F. Beebe
• 2025/10/31 Re: Hard Rust requirements from May onward Julian Andres Klode
• 2025/10/31 Bug#1119819: mesa: FTBFS on alpha, hppa, m68k, sh4: R600 Gallium driver configured to require LLVM Simon McVittie
• 2025/10/31 Re: Hard Rust requirements from May onward Jeffrey Walton
• 2025/10/31 Hard Rust requirements from May onward Julian Andres Klode
• 2025/10/30 Re: Planned obsolescence ? Riccardo Mottola
• 2025/10/29 scpiy m68k build failure Matthias Klose
• 2025/10/28 Re: Architecture baseline for Forky Peter Green
• 2025/10/28 Re: Re: Architecture baseline for Forky John Klos
• 2025/10/28 Re: Planned obsolescence ? (was: Re: Architecture baseline for Forky) Diederik de Haas
• 2025/10/28 Re: Planned obsolescence ? (was: Re: Architecture baseline for Forky) Diederik de Haas
• 2025/10/28 Re: Planned obsolescence ? (was: Re: Architecture baseline for Forky) Marc Haber
• 2025/10/28 AW: Re: Planned obsolescence ? (was: Re: Architecture baseline for Forky) Jan-Daniel Kaplanski
• 2025/10/28 Re: Planned obsolescence ? (was: Re: Architecture baseline for Forky) Marc Haber
• 2025/10/28 Re: Planned obsolescence ? (was: Re: Architecture baseline for Forky) John Paul Adrian Glaubitz
• 2025/10/28 Re: Planned obsolescence ? (was: Re: Architecture baseline for Forky) John Paul Adrian Glaubitz
• 2025/10/28 Re: Architecture baseline for Forky Marc Haber
• 2025/10/28 Re: Planned obsolescence ? (was: Re: Architecture baseline for Forky) Marc Haber
• 2025/10/28 Re: Re: Architecture baseline for Forky Hermann . Lauer
• 2025/10/28 Planned obsolescence ? (was: Re: Architecture baseline for Forky) Romain Dolbeau
• 2025/10/28 Re: Architecture baseline for Forky Kurt Roeckx
• 2025/10/28 Re: Architecture baseline for Forky Sicelo
• 2025/10/27 Re: Architecture baseline for Forky John Klos
• 2025/10/27 Re: Architecture baseline for Forky Milan Kupcevic
• 2025/10/27 Re: Architecture baseline for Forky Rob Landley
• 2025/10/27 Re: Architecture baseline for Forky Rob Landley
• 2025/10/27 Re: Architecture baseline for Forky kiruthikaanbusuresh
• 2025/10/27 Re: Architecture baseline for Forky Marcin Juszkiewicz
• 2025/10/27 Re: Architecture baseline for Forky Aurelien Jarno
• 2025/10/27 Re: Architecture baseline for Forky John Paul Adrian Glaubitz
• 2025/10/27 Re: Architecture baseline for Forky Gerardo Ballabio
• 2025/10/27 Re: Architecture baseline for Forky Geert Uytterhoeven
• 2025/10/26 Re: Architecture baseline for Forky Tony Rodriguez
• 2025/10/26 Re: Architecture baseline for Forky Simon Richter
• 2025/10/26 Re: Architecture baseline for Forky Tony Rodriguez
• 2025/10/26 Re: Architecture baseline for Forky Jan-Daniel Kaplanski
• 2025/10/26 Re: Architecture baseline for Forky Marco d'Itri
• 2025/10/26 Re: Architecture baseline for Forky Tony Rodriguez
• 2025/10/26 Architecture baseline for Forky Bastian Blank
• 2025/10/22 Re: Bug#1111823: dupeguru FTBFS on m68k Stefano Rivera
• 2025/10/10 Bug#1117741: python3.14: Please include patch to fix build with GCC 15 on m68k John Paul Adrian Glaubitz
• 2025/09/07 quick question Miguel Crovari
• 2025/09/03 Re: qemu-user viability (was Re: [SECURITY] [DSA 5983-1] qemu security update) Geert Uytterhoeven
• 2025/09/03 Re: Removing dpkg arch definition for tos-mint? Thorsten Glaser
• 2025/08/24 Re: qemu-user viability (was Re: [SECURITY] [DSA 5983-1] qemu security update) Rob Landley
• 2025/08/23 Re: qemu-user viability (was Re: [SECURITY] [DSA 5983-1] qemu security update) Bastian Blank
• 2025/08/23 Re: qemu-user security trade-offs by dynamic configuration Michael Tokarev
• 2025/08/23 Re: qemu-user security trade-offs by dynamic configuration John Scott
• 2025/08/23 Re: qemu-user lost its entire viability Michael Tokarev
• 2025/08/23 Re: qemu-user lost its entire viability Thorsten Glaser
• 2025/08/23 Re: qemu-user lost its entire viability Michael Tokarev
• 2025/08/23 Re: qemu-user lost its entire viability Thorsten Glaser
• 2025/08/23 Re: qemu-user viability Michael Tokarev
• 2025/08/23 Re: qemu-user viability Thorsten Glaser
• 2025/08/23 Re: qemu-user viability (was Re: [SECURITY] [DSA 5983-1] qemu security update) Michael Tokarev
• 2025/08/23 Re: qemu-user viability (was Re: [SECURITY] [DSA 5983-1] qemu security update) John Paul Adrian Glaubitz
• 2025/08/23 qemu-user viability (was Re: [SECURITY] [DSA 5983-1] qemu security update) Thorsten Glaser
• 2025/08/23 Re: [PATCH 1/1] hung_task: fix warnings by enforcing alignment on lock structures John Paul Adrian Glaubitz
• 2025/06/23 Re: Preliminary results - was: Re: Question on BIGGEST_ALIGNMENT in GCC on NetBSD/m68k Geert Uytterhoeven
• 2025/06/22 Re: Preliminary results - was: Re: Question on BIGGEST_ALIGNMENT in GCC on NetBSD/m68k John Paul Adrian Glaubitz
• 2025/06/22 Re: Preliminary results - was: Re: Question on BIGGEST_ALIGNMENT in GCC on NetBSD/m68k Eero Tamminen
• 2025/06/19 Re: Question on BIGGEST_ALIGNMENT in GCC on NetBSD/m68k Jason Thorpe
• 2025/06/18 Re: Question on BIGGEST_ALIGNMENT in GCC on NetBSD/m68k Greg Ungerer
• 2025/06/18 Re: Question on BIGGEST_ALIGNMENT in GCC on NetBSD/m68k Finn Thain
• 2025/06/18 Re: Question on BIGGEST_ALIGNMENT in GCC on NetBSD/m68k Greg Ungerer
• 2025/06/18 Re: Question on BIGGEST_ALIGNMENT in GCC on NetBSD/m68k Finn Thain
• 2025/06/18 Re: Question on BIGGEST_ALIGNMENT in GCC on NetBSD/m68k Finn Thain
• 2025/06/18 Re: Question on BIGGEST_ALIGNMENT in GCC on NetBSD/m68k Finn Thain
• 2025/06/18 Re: Question on BIGGEST_ALIGNMENT in GCC on NetBSD/m68k Greg Ungerer
• 2025/06/18 Re: Question on BIGGEST_ALIGNMENT in GCC on NetBSD/m68k John Paul Adrian Glaubitz
• 2025/06/18 Re: Question on BIGGEST_ALIGNMENT in GCC on NetBSD/m68k Geert Uytterhoeven
• 2025/06/18 Re: Question on BIGGEST_ALIGNMENT in GCC on NetBSD/m68k Greg Ungerer
• 2025/06/18 Re: Question on BIGGEST_ALIGNMENT in GCC on NetBSD/m68k John Paul Adrian Glaubitz
• 2025/06/18 Re: Question on BIGGEST_ALIGNMENT in GCC on NetBSD/m68k Finn Thain
• 2025/06/18 Re: Question on BIGGEST_ALIGNMENT in GCC on NetBSD/m68k John Paul Adrian Glaubitz
• 2025/06/18 Re: Question on BIGGEST_ALIGNMENT in GCC on NetBSD/m68k Geert Uytterhoeven
• 2025/06/18 Re: Question on BIGGEST_ALIGNMENT in GCC on NetBSD/m68k John Paul Adrian Glaubitz
• 2025/06/18 Re: Question on BIGGEST_ALIGNMENT in GCC on NetBSD/m68k Geert Uytterhoeven
• 2025/06/18 Re: Question on BIGGEST_ALIGNMENT in GCC on NetBSD/m68k John Paul Adrian Glaubitz
• 2025/06/18 Re: Question on BIGGEST_ALIGNMENT in GCC on NetBSD/m68k John Paul Adrian Glaubitz
• 2025/06/17 Re: Question on BIGGEST_ALIGNMENT in GCC on NetBSD/m68k Finn Thain
• 2025/06/17 Re: Question on BIGGEST_ALIGNMENT in GCC on NetBSD/m68k Finn Thain
• 2025/06/17 Re: Tuple and changes for m68k with -malign-int John Paul Adrian Glaubitz
• 2025/06/17 Re: Tuple and changes for m68k with -malign-int Geert Uytterhoeven
• 2025/06/17 Re: Tuple and changes for m68k with -malign-int John Paul Adrian Glaubitz
• 2025/06/17 Re: Tuple and changes for m68k with -malign-int Geert Uytterhoeven
• 2025/06/17 Re: Tuple and changes for m68k with -malign-int John Paul Adrian Glaubitz
• 2025/06/17 Re: Tuple and changes for m68k with -malign-int Geert Uytterhoeven
• 2025/06/17 Re: Tuple and changes for m68k with -malign-int Geert Uytterhoeven
• 2025/06/17 Re: Tuple and changes for m68k with -malign-int John Paul Adrian Glaubitz
• 2025/06/16 Preliminary results - was: Re: Question on BIGGEST_ALIGNMENT in GCC on NetBSD/m68k John Paul Adrian Glaubitz
• 2025/06/16 Re: Question on BIGGEST_ALIGNMENT in GCC on NetBSD/m68k John Paul Adrian Glaubitz
• 2025/06/16 Re: Question on BIGGEST_ALIGNMENT in GCC on NetBSD/m68k Jason Thorpe
• 2025/06/16 Re: Question on BIGGEST_ALIGNMENT in GCC on NetBSD/m68k Jason Thorpe
• 2025/06/16 Re: Question on BIGGEST_ALIGNMENT in GCC on NetBSD/m68k Geert Uytterhoeven
• 2025/06/16 Re: Question on BIGGEST_ALIGNMENT in GCC on NetBSD/m68k John Paul Adrian Glaubitz
• 2025/06/16 Re: Question on BIGGEST_ALIGNMENT in GCC on NetBSD/m68k Geert Uytterhoeven
• 2025/06/16 Re: Question on BIGGEST_ALIGNMENT in GCC on NetBSD/m68k Laurent Vivier
• 2025/06/16 Re: Question on BIGGEST_ALIGNMENT in GCC on NetBSD/m68k John Paul Adrian Glaubitz
• 2025/06/16 Re: Question on BIGGEST_ALIGNMENT in GCC on NetBSD/m68k John Paul Adrian Glaubitz

• Earlier messages