From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Finn Thain <fthain@linux-m68k.org>,
Florian Weimer <fweimer@redhat.com>,
James Le Cuirot <chewi@aura-online.co.uk>,
debian-68k <debian-68k@lists.debian.org>,
linux-m68k <linux-m68k@vger.kernel.org>,
Libc-help <libc-help@sourceware.org>
Subject: Re: Tuple and changes for m68k with -malign-int
Date: Tue, 20 May 2025 12:05:06 +0200 [thread overview]
Message-ID: <5c9c0b3487a84f5409ea2a83cecaf06c601b51d5.camel@physik.fu-berlin.de> (raw)
In-Reply-To: <CAMuHMdWVjDGYW2SerNV5ov6jX1pPNw_j1=qpawBCJph18_SE2w@mail.gmail.com>
On Tue, 2025-05-20 at 11:58 +0200, Geert Uytterhoeven wrote:
> On Tue, 20 May 2025 at 10:38, John Paul Adrian Glaubitz
> <glaubitz@physik.fu-berlin.de> wrote:
> > And I also don't understand why this is even an issue. If someone insists
> > on using 2 bytes alignment, just stick to your old chroot. If you're not
>
> What about kernel/userland compatibility?
What about it? This is about userland.
> > interested in new, "fancy" packages, just don't upgrade or install Debian
> > Etch or similar. Changing the default alignment does not affect existing
> > software.
>
> What about existing software that is aware the minimum alignment is
> 2-bytes on m68k?
Can you name some cases? I would love to add these to my list.
Thanks,
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer
`. `' Physicist
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
next prev parent reply other threads:[~2025-05-20 10:05 UTC|newest]
Thread overview: 85+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <e9035006d50933fb02727fa373629cc821784f6c.camel@aura-online.co.uk>
2023-08-26 10:51 ` Tuple and changes for m68k with -malign-int John Paul Adrian Glaubitz
2023-08-26 19:24 ` Richard
2023-08-26 20:43 ` James Le Cuirot
2023-08-28 6:54 ` Geert Uytterhoeven
2023-08-28 10:57 ` John Paul Adrian Glaubitz
2023-08-28 12:11 ` Richard
2023-08-28 12:22 ` Geert Uytterhoeven
2023-08-28 12:46 ` John Paul Adrian Glaubitz
2023-08-27 0:46 ` Finn Thain
2023-08-27 9:20 ` James Le Cuirot
2023-08-27 11:27 ` Richard
2023-08-28 7:00 ` Geert Uytterhoeven
2023-08-28 11:26 ` Richard
2023-08-28 11:40 ` Geert Uytterhoeven
2023-08-28 20:16 ` Richard
2023-08-29 6:52 ` Geert Uytterhoeven
2023-08-28 6:56 ` Geert Uytterhoeven
2023-08-28 11:13 ` John Paul Adrian Glaubitz
2023-08-29 1:12 ` Finn Thain
2023-08-28 11:10 ` John Paul Adrian Glaubitz
2023-08-28 12:44 ` Adhemerval Zanella Netto
2023-08-28 12:50 ` John Paul Adrian Glaubitz
2023-08-28 13:17 ` Andreas Schwab
2023-08-29 10:51 ` John Paul Adrian Glaubitz
2023-08-29 15:27 ` Geert Uytterhoeven
2023-08-28 13:29 ` James Le Cuirot
2023-08-29 10:54 ` John Paul Adrian Glaubitz
2023-08-29 21:53 ` Karoly Balogh
2023-08-30 1:33 ` Jeffrey Walton
2023-08-29 1:14 ` Finn Thain
2023-08-29 8:52 ` Eero Tamminen
2024-05-15 17:08 ` Python requires 32-bit alignment now - was: " John Paul Adrian Glaubitz
2025-05-18 7:09 ` John Paul Adrian Glaubitz
2025-05-18 14:39 ` Antonio Vargas Gonzalez
2025-05-18 15:07 ` John Paul Adrian Glaubitz
2025-05-19 7:42 ` Geert Uytterhoeven
2025-05-19 7:54 ` John Paul Adrian Glaubitz
2025-05-19 8:03 ` Andreas Schwab
2025-05-19 8:18 ` John Paul Adrian Glaubitz
2025-05-19 8:25 ` Geert Uytterhoeven
2025-05-19 8:43 ` John Paul Adrian Glaubitz
2025-05-19 8:07 ` Geert Uytterhoeven
2025-05-19 8:14 ` Florian Weimer
2025-05-19 8:24 ` John Paul Adrian Glaubitz
2025-05-19 21:51 ` James Le Cuirot
2025-05-20 9:39 ` John Paul Adrian Glaubitz
2025-05-21 9:15 ` James Le Cuirot
2025-05-21 9:19 ` John Paul Adrian Glaubitz
2025-05-19 21:59 ` Finn Thain
2025-05-20 7:55 ` John Paul Adrian Glaubitz
2025-05-20 8:24 ` Geert Uytterhoeven
2025-05-20 8:37 ` John Paul Adrian Glaubitz
2025-05-20 9:46 ` Finn Thain
2025-05-20 9:56 ` John Paul Adrian Glaubitz
2025-05-20 9:58 ` Geert Uytterhoeven
2025-05-20 10:05 ` John Paul Adrian Glaubitz [this message]
2025-05-20 10:09 ` Geert Uytterhoeven
2025-05-20 10:12 ` John Paul Adrian Glaubitz
2025-05-20 22:13 ` John Paul Adrian Glaubitz
2025-05-21 0:29 ` Finn Thain
2025-05-21 1:59 ` John Klos
2025-05-21 5:18 ` Finn Thain
2025-05-26 5:25 ` Finn Thain
2025-05-21 7:28 ` Finn Thain
2025-05-21 9:56 ` John Paul Adrian Glaubitz
2025-05-21 14:09 ` Debian subset suitable for m68k (was: Tuple and changes for m68k with -malign-int) Eero Tamminen
2025-05-21 17:54 ` John Paul Adrian Glaubitz
2025-05-21 22:14 ` Eero Tamminen
2025-06-17 7:02 ` Tuple and changes for m68k with -malign-int Geert Uytterhoeven
2025-06-17 7:25 ` John Paul Adrian Glaubitz
2025-06-17 7:40 ` Geert Uytterhoeven
2025-06-17 9:48 ` John Paul Adrian Glaubitz
2025-06-17 9:59 ` Geert Uytterhoeven
2025-06-17 10:13 ` John Paul Adrian Glaubitz
2025-06-17 11:21 ` Geert Uytterhoeven
2025-06-17 11:37 ` John Paul Adrian Glaubitz
2025-05-20 9:39 ` Finn Thain
2025-05-20 9:43 ` John Paul Adrian Glaubitz
2025-05-20 9:55 ` Finn Thain
2025-05-20 10:18 ` John Paul Adrian Glaubitz
2025-05-20 11:03 ` Finn Thain
2025-05-20 11:13 ` John Paul Adrian Glaubitz
2025-05-21 0:14 ` Finn Thain
2025-05-21 17:36 John Klos
2025-05-21 23:50 ` Finn Thain
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=5c9c0b3487a84f5409ea2a83cecaf06c601b51d5.camel@physik.fu-berlin.de \
--to=glaubitz@physik.fu-berlin.de \
--cc=chewi@aura-online.co.uk \
--cc=debian-68k@lists.debian.org \
--cc=fthain@linux-m68k.org \
--cc=fweimer@redhat.com \
--cc=geert@linux-m68k.org \
--cc=libc-help@sourceware.org \
--cc=linux-m68k@vger.kernel.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).