gmane.linux.debian.ports.68k archive

406 archived articles, newest first (page 2 of 5). Latest articles →

Re: Preliminary results - was: Re: Question on BIGGEST_ALIGNMENT in GCC on NetBSD/m68k
Tue, 6 Jan 2026 14:34:02 +0100 (CET)
Kolbjørn Barmen <[email protected]> • #16715
Re: Preliminary results - was: Re: Question on BIGGEST_ALIGNMENT in GCC on NetBSD/m68k
Tue, 06 Jan 2026 14:40:33 +0100
John Paul Adrian Glaubitz <[email protected]> • #16714
Re: Bug#1066890: rdma-core: don't build docs on minor arches (-DNO_MAN_PAGES=1)
Thu, 01 Jan 2026 13:06:06 +0100
John Paul Adrian Glaubitz <[email protected]> • #16713
Re: Bug#1066890: rdma-core: don't build docs on minor arches (-DNO_MAN_PAGES=1)
Thu, 01 Jan 2026 12:27:16 +0100
John Paul Adrian Glaubitz <[email protected]> • #16712
Re: qemu-system-sh4eb build has something hinky in the ethernet
Wed, 31 Dec 2025 02:04:04 -0600
Rob Landley <[email protected]> • #16711
Contacto
Mon, 29 Dec 2025 10:53:41 -0600
"Alejandro Sanchez" <[email protected]> • #16710
Re: Bug#1124228: libavif: Build-depends on libgav1 which build-depends on architecture-is-little-endian
Mon, 29 Dec 2025 09:39:49 +0100
John Paul Adrian Glaubitz <[email protected]> • #16709
Bug#1124228: libavif: Build-depends on libgav1 which build-depends on architecture-is-little-endian
Mon, 29 Dec 2025 02:03:08 +0100
John Paul Adrian Glaubitz <[email protected]> • #16708
Bug#1123577: nmu: mesa_25.2.8-2: +b3 on !amd64
Thu, 18 Dec 2025 11:17:17 +0000
Simon McVittie <[email protected]> • #16707
Bug#1088168: gimp 3 FTBFS on big-endian
Mon, 15 Dec 2025 23:17:31 -0500
Jeremy Bícha <[email protected]> • #16706
Bug#1088168: gimp 3 FTBFS on big-endian
Sun, 14 Dec 2025 14:45:59 -0500
Jeremy Bícha <[email protected]> • #16705
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)
Fri, 12 Dec 2025 16:01:25 +0100
Andreas Tille <[email protected]> • #16704
Re: Bug#1122336: libreoffice: Smoketest fails on hppa and powerpc due to missing soffice.sh
Thu, 11 Dec 2025 20:02:08 +0100
Rene Engelhard <[email protected]> • #16703
Re: Bug#1122336: libreoffice: Smoketest fails on hppa and powerpc due to missing soffice.sh
Thu, 11 Dec 2025 18:00:55 +0100
Rene Engelhard <[email protected]> • #16702
Re: Bug#1122336: libreoffice: Smoketest fails on hppa and powerpc due to missing soffice.sh
Thu, 11 Dec 2025 17:57:13 +0100
Rene Engelhard <[email protected]> • #16701
Re: Bug#1122336: libreoffice: Smoketest fails on hppa and powerpc due to missing soffice.sh
Thu, 11 Dec 2025 17:53:27 +0100
John Paul Adrian Glaubitz <[email protected]> • #16700
Re: Bug#1122336: libreoffice: Smoketest fails on hppa and powerpc due to missing soffice.sh
Thu, 11 Dec 2025 17:45:11 +0100
Rene Engelhard <[email protected]> • #16699
Re: Bug#1122336: libreoffice: Smoketest fails on hppa and powerpc due to missing soffice.sh
Thu, 11 Dec 2025 17:39:39 +0100
Rene Engelhard <[email protected]> • #16698
Re: Bug#1122336: libreoffice: Smoketest fails on hppa and powerpc due to missing soffice.sh
Thu, 11 Dec 2025 17:35:31 +0100
John Paul Adrian Glaubitz <[email protected]> • #16697
Re: Bug#1122336: libreoffice: Smoketest fails on hppa and powerpc due to missing soffice.sh
Thu, 11 Dec 2025 17:29:45 +0100
Rene Engelhard <[email protected]> • #16696
Bug#1122336: libreoffice: Smoketest fails on hppa and powerpc due to missing soffice.sh
Thu, 11 Dec 2025 17:21:29 +0100
Rene Engelhard <[email protected]> • #16695
Re: Bug#1122336: libreoffice: Smoketest fails on hppa and powerpc due to missing soffice.sh
Thu, 11 Dec 2025 17:03:14 +0100
John Paul Adrian Glaubitz <[email protected]> • #16694
Bug#1122336: libreoffice: Smoketest fails on hppa and powerpc due to missing soffice.sh
Wed, 10 Dec 2025 08:40:54 +0100
John Paul Adrian Glaubitz <[email protected]> • #16693
Bug#1122205: RM: rhonabwy -- ROM; upstream is no longer maintained and depends on obsolete packages, FTBFS with gnutls 3.8.11
Mon, 08 Dec 2025 13:34:17 -0500
Nicolas Mora <[email protected]> • #16692
Re: Bug#1121969: python3.14: Please build with -O1 on m68k to workaround interpretor lockups
Fri, 05 Dec 2025 20:13:00 +0100
John Paul Adrian Glaubitz <[email protected]> • #16691
Re: Bug#1121969: python3.14: Please build with -O1 on m68k to workaround interpretor lockups
Fri, 5 Dec 2025 20:56:33 +0200
Eero Tamminen <[email protected]> • #16690
Bug#1121974: python3.13: Please build with -O1 on m68k to workaround interpretor lockups
Fri, 05 Dec 2025 13:11:49 +0100
John Paul Adrian Glaubitz <[email protected]> • #16689
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)
Fri, 05 Dec 2025 11:54:03 +0100
Andreas Tille <[email protected]> • #16688
Bug#1121969: python3.14: Please build with -O1 on m68k to workaround interpretor lockups
Fri, 05 Dec 2025 11:45:27 +0100
John Paul Adrian Glaubitz <[email protected]> • #16687
Re: Architecture baseline for Forky
Thu, 4 Dec 2025 17:01:10 -0600
Rob Landley <[email protected]> • #16686
Re: Bug#1121780: Please revert 3.13.9 version bump to help m68k
Wed, 3 Dec 2025 05:32:10 -0500
Jeffrey Walton <[email protected]> • #16685
Re: Bug#1121780: Please revert 3.13.9 version bump to help m68k
Wed, 03 Dec 2025 11:08:00 +0100
John Paul Adrian Glaubitz <[email protected]> • #16684
Re: Bug#1121780: Please revert 3.13.9 version bump to help m68k
Tue, 02 Dec 2025 15:31:20 +0100
John Paul Adrian Glaubitz <[email protected]> • #16683
Bug#1121780: Please revert 3.13.9 version bump to help m68k
Tue, 02 Dec 2025 16:25:35 +0200
Adrian Bunk <[email protected]> • #16682
OMP fixed in the llvm-21 packaging
Tue, 2 Dec 2025 09:28:28 +0100
Matthias Klose <[email protected]> • #16681
64mb limitation of qemu-system-sh4 board
Mon, 24 Nov 2025 08:31:03 +0100
Philippe Mathieu-Daudé <[email protected]> • #16680
Re: qemu-system-sh4eb build has something hinky in the ethernet
Mon, 24 Nov 2025 08:18:58 +0100
Philippe Mathieu-Daudé <[email protected]> • #16679
Re: 64mb limitation of qemu-system-sh4 board
Mon, 24 Nov 2025 08:33:11 +0100
John Paul Adrian Glaubitz <[email protected]> • #16678
gcc-16, first packaging bits
Sun, 23 Nov 2025 13:12:30 +0100
Matthias Klose <[email protected]> • #16677
Bug#1100980: internal compiler error while building sqlite3 for m68k
Sat, 22 Nov 2025 10:38:14 +0100
Matthias Klose <[email protected]> • #16676
What does the publishing charged?
Thu, 20 Nov 2025 21:00:58 +0500
"stephanie M.pigg" <[email protected]> • #16675
Re: Architecture baseline for Forky
Wed, 12 Nov 2025 23:05:44 +0100
Lucas Nussbaum <[email protected]> • #16674
Re: Architecture baseline for Forky
Wed, 12 Nov 2025 20:27:20 +0200
Adrian Bunk <[email protected]> • #16673
Re: Architecture baseline for Forky
Thu, 6 Nov 2025 08:27:28 +0000
Holger Levsen <[email protected]> • #16672
Re: Architecture baseline for Forky
Wed, 5 Nov 2025 20:42:08 +0100
Lucas Nussbaum <[email protected]> • #16671
Re: Hard Rust requirements from May onward
Wed, 05 Nov 2025 14:56:56 +0000
Sean Whitton <[email protected]> • #16670
Re: Bug#1118058: scipy: m68k fails: sparseto ols/bsr.h unable to find a register to spill in class ‘ADDR_REGS’
Wed, 05 Nov 2025 14:54:25 +0100
Drew Parsons <[email protected]> • #16669
Re: Bug#1118058: scipy: m68k fails: sparsetools/bsr.h unable to find a register to spill in class ‘ADDR_REGS’
Wed, 05 Nov 2025 14:47:17 +0100
John Paul Adrian Glaubitz <[email protected]> • #16668
Bug#1118058: scipy: m68k fails: sparsetools/bsr.h unable to find a register to spill in class ‘ADDR_REGS’
Wed, 05 Nov 2025 14:33:42 +0100
Drew Parsons <[email protected]> • #16667
Re: Planned obsolescence ? (OpenBSD)
Wed, 05 Nov 2025 10:50:59 +0100
Philipp Kern <[email protected]> • #16666
Re: Planned obsolescence ? (*BSD, Rust)
Tue, 4 Nov 2025 09:49:27 -0600
Falco Girgis <[email protected]> • #16665
Re: Planned obsolescence ? (OpenBSD)
Tue, 4 Nov 2025 09:19:02 -0500
John David Anglin <[email protected]> • #16664
Re: Planned obsolescence ? (*BSD, Rust)
Tue, 4 Nov 2025 12:57:25 +0100
Christopher Huhn <[email protected]> • #16663
Re: Planned obsolescence ? (*BSD, Rust)
Tue, 04 Nov 2025 12:56:58 +0100
"Dr. Arne Babenhauserheide" <[email protected]> • #16662
Re: Planned obsolescence ?
Tue, 4 Nov 2025 12:32:02 +0100
Riccardo Mottola <[email protected]> • #16661
Re: Planned obsolescence ? (*BSD, Rust)
Tue, 4 Nov 2025 09:48:43 +0100
Riccardo Mottola <[email protected]> • #16660
Re: Planned obsolescence ?
Tue, 04 Nov 2025 09:22:10 +0100 (CET)
Jaromír Cápík <[email protected]> • #16659
Re: Planned obsolescence ? (*BSD, Rust)
Mon, 3 Nov 2025 17:19:25 -0600
David Starner <[email protected]> • #16658
Re: Planned obsolescence ? (*BSD, Rust)
Mon, 3 Nov 2025 23:20:01 +0100
Jan-Daniel Kaplanski <[email protected]> • #16657
Re: Planned obsolescence ? (*BSD, Rust)
Mon, 3 Nov 2025 15:16:40 -0600
David Starner <[email protected]> • #16656
Re: Planned obsolescence ? (*BSD, Rust)
Mon, 3 Nov 2025 01:04:52 +0100
Jan-Daniel Kaplanski <[email protected]> • #16655
Re: Hard Rust requirements from May onward
Sun, 2 Nov 2025 18:01:50 -0500
Jeffrey Walton <[email protected]> • #16654
Re: Planned obsolescence ? (OpenBSD)
Sun, 2 Nov 2025 17:23:52 -0500
Paul Tagliamonte <[email protected]> • #16653
Re: Planned obsolescence ? (OpenBSD)
Sun, 02 Nov 2025 21:35:49 +0000
[email protected] • #16652
Re: Hard Rust requirements from May onward
Sun, 02 Nov 2025 17:38:36 +0100
Joerg Jaspert <[email protected]> • #16651
Re: Hard Rust requirements from May onward
Sun, 2 Nov 2025 17:21:45 +0100
Julian Andres Klode <[email protected]> • #16650
Re: Hard Rust requirements from May onward
Sun, 2 Nov 2025 14:30:10 +0000
Bill Allombert <[email protected]> • #16649
Re: Hard Rust requirements from May onward
Sun, 02 Nov 2025 13:08:06 +0100
Joerg Jaspert <[email protected]> • #16648
Re: Hard Rust requirements from May onward
Sat, 1 Nov 2025 10:12:29 -0400
Paul Tagliamonte <[email protected]> • #16647
Re: Hard Rust requirements from May onward
Sat, 1 Nov 2025 10:10:06 -0400
Paul Tagliamonte <[email protected]> • #16646
Re: Hard Rust requirements from May onward
Fri, 31 Oct 2025 16:09:04 -0600
"Nelson H. F. Beebe" <[email protected]> • #16645
Re: Hard Rust requirements from May onward
Fri, 31 Oct 2025 22:39:24 +0100
Julian Andres Klode <[email protected]> • #16644
Re: Hard Rust requirements from May onward
Fri, 31 Oct 2025 17:16:23 -0400
Jeffrey Walton <[email protected]> • #16643
Bug#1119819: mesa: FTBFS on alpha, hppa, m68k, sh4: R600 Gallium driver configured to require LLVM
Fri, 31 Oct 2025 21:14:38 +0000
Simon McVittie <[email protected]> • #16642
Hard Rust requirements from May onward
Fri, 31 Oct 2025 21:48:46 +0100
Julian Andres Klode <[email protected]> • #16641
Re: Planned obsolescence ?
Thu, 30 Oct 2025 09:58:04 +0100
Riccardo Mottola <[email protected]> • #16640
Bug#1118058: scpiy m68k build failure
Wed, 29 Oct 2025 10:34:22 +0100
Matthias Klose <[email protected]> • #16639
Re: Architecture baseline for Forky
Tue, 28 Oct 2025 19:57:36 +0000
Peter Green <[email protected]> • #16638
Re: Re: Architecture baseline for Forky
Tue, 28 Oct 2025 17:41:43 +0000 (UTC)
John Klos <[email protected]> • #16637
Re: Planned obsolescence ? (was: Re: Architecture baseline for Forky)
Tue, 28 Oct 2025 15:40:51 +0100
"Diederik de Haas" <[email protected]> • #16636
Re: Planned obsolescence ? (was: Re: Architecture baseline for Forky)
Tue, 28 Oct 2025 15:00:24 +0100
"Diederik de Haas" <[email protected]> • #16635
Re: Planned obsolescence ? (was: Re: Architecture baseline for Forky)
Tue, 28 Oct 2025 15:03:54 +0100
Marc Haber <[email protected]> • #16634
AW: Re: Planned obsolescence ? (was: Re: Architecture baseline for Forky)
Tue, 28 Oct 2025 09:35:00 +0000 (UTC)
Jan-Daniel Kaplanski <[email protected]> • #16633
Re: Planned obsolescence ? (was: Re: Architecture baseline for Forky)
Tue, 28 Oct 2025 10:48:20 +0100
Marc Haber <[email protected]> • #16632
Re: Planned obsolescence ? (was: Re: Architecture baseline for Forky)
Tue, 28 Oct 2025 10:32:36 +0100
John Paul Adrian Glaubitz <[email protected]> • #16631
Re: Planned obsolescence ? (was: Re: Architecture baseline for Forky)
Tue, 28 Oct 2025 10:30:57 +0100
John Paul Adrian Glaubitz <[email protected]> • #16630
Re: Architecture baseline for Forky
Tue, 28 Oct 2025 10:15:37 +0100
Marc Haber <[email protected]> • #16629
Re: Planned obsolescence ? (was: Re: Architecture baseline for Forky)
Tue, 28 Oct 2025 10:07:07 +0100
Marc Haber <[email protected]> • #16628
Re: Re: Architecture baseline for Forky
Tue, 28 Oct 2025 09:39:44 +0100
[email protected] • #16627
Planned obsolescence ? (was: Re: Architecture baseline for Forky)
Tue, 28 Oct 2025 09:59:11 +0100
Romain Dolbeau <[email protected]> • #16626
Re: Architecture baseline for Forky
Tue, 28 Oct 2025 00:06:25 +0100
Kurt Roeckx <[email protected]> • #16625
Re: Architecture baseline for Forky
Tue, 28 Oct 2025 09:18:38 +0200
Sicelo <[email protected]> • #16624
Re: Architecture baseline for Forky
Mon, 27 Oct 2025 23:52:00 +0000 (UTC)
John Klos <[email protected]> • #16623
Re: Architecture baseline for Forky
Mon, 27 Oct 2025 17:38:57 -0400
Milan Kupcevic <[email protected]> • #16622
Re: Architecture baseline for Forky
Mon, 27 Oct 2025 15:25:30 -0500
Rob Landley <[email protected]> • #16621
Re: Architecture baseline for Forky
Mon, 27 Oct 2025 15:13:45 -0500
Rob Landley <[email protected]> • #16620
Re: Architecture baseline for Forky
Mon, 27 Oct 2025 16:00:11 +0530
kiruthikaanbusuresh <[email protected]> • #16619
Re: Architecture baseline for Forky
Mon, 27 Oct 2025 11:20:29 +0100
Marcin Juszkiewicz <[email protected]> • #16618
Re: Architecture baseline for Forky
Mon, 27 Oct 2025 11:20:06 +0100
Aurelien Jarno <[email protected]> • #16617
Re: Architecture baseline for Forky
Mon, 27 Oct 2025 10:33:28 +0100
John Paul Adrian Glaubitz <[email protected]> • #16616
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.