linux-m68k.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: Finn Thain <fthain@linux-m68k.org>
Cc: Thorsten Glaser <tg@debian.org>, Arnd Bergmann <arnd@arndb.de>,
	linux-m68k	 <linux-m68k@vger.kernel.org>,
	debian-68k <debian-68k@lists.debian.org>,
	 James Le Cuirot <chewi@aura-online.co.uk>,
	Sam James <sam@gentoo.org>,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	 Andreas Schwab <schwab@linux-m68k.org>
Subject: Re: Plan needed for switching m68k to 32-bit alignment
Date: Wed, 13 Nov 2024 13:53:38 +0100	[thread overview]
Message-ID: <2414fe9be8e6b1339c178678d4c58be3f160db6d.camel@physik.fu-berlin.de> (raw)
In-Reply-To: <8d01228e-d6c6-6d10-f60d-b353b341e4b4@linux-m68k.org>

On Mon, 2024-10-28 at 19:49 +1100, Finn Thain wrote:
> > Here is the current top of the list of packages that won't build on m68k 
> > because of the 2-byte alignment issue:
> > 
> >    2814 cargo:m68k
> >     900 ghc:m68k
> >     261 gccgo-14:m68k
> >     241 libqt5core5a:m68k
> >     181 architecture-is-64-bit:m68k
> >     117 libglib2.0-0:m68k
> >      81 libcompiler-libs-ocaml-dev-0a396:m68k
> >      81 golang-go:m68k
> >      71 wx3.2-headers:m68k
> >      57 qt6-base-dev:m68k
> >      57 python3:m68k
> >      46 libamd2:m68k
> > 
> > Are you going to fix these for me?
> > 
> 
> Are you the only user?

I am the one who does all the work on Debian/m68k.

> Seriously though, thanks for providing data. Now, if you would link to the 
> upstream refusals for CPython and golang, I'll do what I can to help.

I honestly don't have to justify myself towards you. I will use the Christmas
holidays to make a decision. I will either drop the m68k port from Debian or
just perform a forced switch.

I don't care anymore what you're posting here. You're just wasting my time.

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer
`. `'   Physicist
  `-    GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

  reply	other threads:[~2024-11-13 12:53 UTC|newest]

Thread overview: 71+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-25  6:48 Plan needed for switching m68k to 32-bit alignment John Paul Adrian Glaubitz
2024-10-25  9:06 ` Finn Thain
2024-10-25  9:18   ` John Paul Adrian Glaubitz
2024-10-26  7:31     ` Finn Thain
2024-10-26 22:04       ` Thorsten Glaser
2024-10-27  2:49         ` Finn Thain
2024-10-27  3:08           ` Thorsten Glaser
2024-10-27  3:47             ` Finn Thain
2024-10-27  4:23               ` Thorsten Glaser
2024-10-27  6:16                 ` Finn Thain
2024-10-27 13:15                   ` Arnd Bergmann
2024-10-28  3:07                     ` Thorsten Glaser
2024-10-28  4:51                       ` Finn Thain
2024-10-28  8:09                         ` John Paul Adrian Glaubitz
2024-10-28  8:49                           ` Finn Thain
2024-11-13 12:53                             ` John Paul Adrian Glaubitz [this message]
2024-10-28  8:03                       ` John Paul Adrian Glaubitz
2024-10-28  8:44                         ` Finn Thain
2024-11-13 12:51                           ` John Paul Adrian Glaubitz
2024-10-28  7:58                     ` John Paul Adrian Glaubitz
2024-10-28  7:55                   ` John Paul Adrian Glaubitz
2024-11-14 16:29                   ` Geert Uytterhoeven
2024-11-15  0:24                     ` Finn Thain
2024-11-15  1:24                       ` Thorsten Glaser
2024-11-15  1:31                         ` Thorsten Glaser
2024-10-28  7:53               ` John Paul Adrian Glaubitz
2024-10-28  7:49             ` John Paul Adrian Glaubitz
2024-10-28  7:47           ` John Paul Adrian Glaubitz
2024-10-28  8:40             ` Finn Thain
2024-11-13 12:50               ` John Paul Adrian Glaubitz
2024-11-13 22:01                 ` Finn Thain
2024-10-28  7:43         ` John Paul Adrian Glaubitz
2024-10-28  7:40       ` John Paul Adrian Glaubitz
2024-10-28  8:29         ` Finn Thain
2024-11-13 12:47           ` John Paul Adrian Glaubitz
2024-11-13 22:52             ` Finn Thain
2024-10-25  9:55 ` Arnd Bergmann
2024-10-25 10:10   ` John Paul Adrian Glaubitz
2024-10-25 10:50     ` Arnd Bergmann
2024-10-25 15:07       ` Andreas Schwab
2024-10-28  7:24         ` John Paul Adrian Glaubitz
2024-10-25 21:38     ` Thorsten Glaser
2024-10-25 22:24       ` Andreas Schwab
2024-10-25 23:42         ` Thorsten Glaser
2024-10-27 13:03           ` Greg Ungerer
2024-10-27 12:58         ` Arnd Bergmann
2024-10-28  3:19           ` Thorsten Glaser
2024-10-28  3:54             ` Greg Ungerer
2024-10-28  7:57           ` John Paul Adrian Glaubitz
2024-10-28  7:30         ` John Paul Adrian Glaubitz
2024-10-26 10:46       ` Geert Uytterhoeven
2024-10-28  7:41         ` John Paul Adrian Glaubitz
2024-10-28  7:26       ` John Paul Adrian Glaubitz
2024-11-14 19:46       ` Geert Uytterhoeven
2024-11-14 22:13         ` Thorsten Glaser
2024-11-14 22:37           ` James Le Cuirot
2024-10-28 18:57   ` Michael Schmitz
2024-10-29  3:39     ` Finn Thain
2024-11-13 12:58       ` John Paul Adrian Glaubitz
2024-11-13 23:12         ` Finn Thain
2024-11-13 12:54     ` John Paul Adrian Glaubitz
2024-11-13 18:36       ` Michael Schmitz
2024-11-13 19:55         ` John Paul Adrian Glaubitz
2024-11-13 20:48           ` Stan Johnson
2024-11-13 21:01             ` John Paul Adrian Glaubitz
2024-11-14 18:07               ` Stan Johnson
2024-11-14 19:28                 ` Geert Uytterhoeven
2024-11-13 20:49           ` John Paul Adrian Glaubitz
2024-11-13 21:33           ` Thorsten Glaser
2024-11-13 23:34             ` Finn Thain
2024-11-14 19:32           ` Geert Uytterhoeven

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2414fe9be8e6b1339c178678d4c58be3f160db6d.camel@physik.fu-berlin.de \
    --to=glaubitz@physik.fu-berlin.de \
    --cc=arnd@arndb.de \
    --cc=chewi@aura-online.co.uk \
    --cc=debian-68k@lists.debian.org \
    --cc=fthain@linux-m68k.org \
    --cc=geert@linux-m68k.org \
    --cc=linux-m68k@vger.kernel.org \
    --cc=sam@gentoo.org \
    --cc=schwab@linux-m68k.org \
    --cc=tg@debian.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).