From: Eli Zaretskii <eliz@gnu.org>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: 50230@debbugs.gnu.org, akrl@sdf.org
Subject: bug#50230: Endian problem with native compilation
Date: Sat, 04 Sep 2021 12:45:04 +0300 [thread overview]
Message-ID: <83o898wu73.fsf@gnu.org> (raw)
In-Reply-To: <87o898vgje.fsf@linux-m68k.org> (message from Andreas Schwab on Sat, 04 Sep 2021 11:25:25 +0200)
> From: Andreas Schwab <schwab@linux-m68k.org>
> Cc: akrl@sdf.org, 50230@debbugs.gnu.org
> Date: Sat, 04 Sep 2021 11:25:25 +0200
>
> On Sep 04 2021, Eli Zaretskii wrote:
>
> > that's one reason why the change didn't fix Emacs on big-endian
> > systems?
>
> It does.
Sorry, I'm not sure I understand: are you saying that change did fix
the problem? I thought you previously said it didn't?
next prev parent reply other threads:[~2021-09-04 9:45 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-27 17:39 bug#50230: Endian problem with native compilation Andreas Schwab
2021-08-30 9:54 ` Andreas Schwab
2021-08-30 13:03 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-08-30 13:13 ` Andreas Schwab
2021-08-30 13:20 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-09-01 12:28 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-09-01 13:19 ` Andreas Schwab
2021-09-01 14:00 ` Eli Zaretskii
2021-09-01 15:13 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-09-01 16:05 ` Eli Zaretskii
2021-09-04 9:15 ` Eli Zaretskii
2021-09-04 9:25 ` Andreas Schwab
2021-09-04 9:45 ` Eli Zaretskii [this message]
2021-09-04 9:49 ` Andreas Schwab
2021-09-04 10:06 ` Eli Zaretskii
2021-09-04 11:01 ` Andreas Schwab
2021-09-04 11:06 ` Eli Zaretskii
2021-11-30 17:02 ` Andrea Corallo
2021-11-30 17:06 ` Andreas Schwab
2021-11-30 17:10 ` Andrea Corallo
2021-11-30 21:05 ` Andreas Schwab
2021-12-01 3:19 ` Eli Zaretskii
2022-08-22 14:47 ` Lars Ingebrigtsen
2022-09-19 19:18 ` Lars Ingebrigtsen
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=83o898wu73.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=50230@debbugs.gnu.org \
--cc=akrl@sdf.org \
--cc=schwab@linux-m68k.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.