Re: Plan needed for switching m68k to 32-bit alignment
- 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
- From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
- Date: Wed, 13 Nov 2024 13:53:38 +0100
- Message-id: <[🔎] 2414fe9be8e6b1339c178678d4c58be3f160db6d.camel@physik.fu-berlin.de>
- In-reply-to: <8d01228e-d6c6-6d10-f60d-b353b341e4b4@linux-m68k.org>
- References: <3a5e171bf42e5273eb8235cba04e8328b19c2ca4.camel@physik.fu-berlin.de> <d95cbe0f-696e-813a-3655-f982531dfb41@linux-m68k.org> <fe7eaef152b4a245c6bab76ae02946a0746bdf65.camel@physik.fu-berlin.de> <eb26c030-5bc9-0e2e-1222-64306bfa7553@linux-m68k.org> <5e8917a2-b7c4-6c06-e63f-1f05eea32120@mirbsd.de> <a07af4eb-efba-d8f1-ace1-06da7a7067c0@linux-m68k.org> <Pine.BSM.4.64L.2410270301550.3007@herc.mirbsd.org> <a6ef54f6-7a3d-78d5-47d1-d4f7fc1e04e2@linux-m68k.org> <Pine.BSM.4.64L.2410270420080.3007@herc.mirbsd.org> <b9ef3e70-6ee0-3e4f-185c-afaa8f512792@linux-m68k.org> <b25dbb5f-6336-4f2d-9d1e-4d5da13a1636@app.fastmail.com> <0c34ba23-5256-0140-59b1-6a5283f6b763@debian.org> <f2377db5-2b39-0e58-4d22-1caee7e8e6a3@linux-m68k.org> <325daee024e5290959c5147346602ac7f0089474.camel@physik.fu-berlin.de> <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 to: