From: Po Lu <luangruo@yahoo.com>
To: Richard Stallman <rms@gnu.org>
Cc: eliz@gnu.org, emacs-devel@gnu.org
Subject: Re: The 'cross' directory
Date: Wed, 09 Aug 2023 11:54:05 +0800 [thread overview]
Message-ID: <87jzu4yioy.fsf@yahoo.com> (raw)
In-Reply-To: <E1qTaA2-000389-9o@fencepost.gnu.org> (Richard Stallman's message of "Tue, 08 Aug 2023 23:47:02 -0400")
Richard Stallman <rms@gnu.org> writes:
> Is it true that cross-compiling Emacs does not work
> except when the target is Emacs?
I presume you meant Android by Emacs. I view this as a feature, not a
problem, because:
> It is supposed to work. Normally autoconf does that automatically.
> What broke it?
Nothing broke it. Emacs never supported cross compilation in the past,
since Emacs is needed on the build machine to compile Lisp and dump
itself.
This arrangement has not changed under Android. Instead, Emacs is
configured once and run on the build machine for the purpose of
byte-compiling Lisp code, before `configure' is rerun with the Android
cross-compiler to generate an undumped C binary that is copied into the
Android installation package. Dumping subsequently takes place when
that package is installed.
next prev parent reply other threads:[~2023-08-09 3:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-07 17:09 The 'cross' directory Eli Zaretskii
2023-08-08 0:51 ` Po Lu
2023-08-09 3:47 ` Richard Stallman
2023-08-09 3:54 ` Po Lu [this message]
2023-08-13 1:43 ` Richard Stallman
2023-08-13 2:10 ` Po Lu
2023-08-13 2:14 ` Emanuel Berg
2023-08-13 5:39 ` Eli Zaretskii
2023-08-15 8:05 ` Helmut Eller
2023-08-15 11:44 ` Eli Zaretskii
2023-08-16 21:32 ` Helmut Eller
2023-08-17 7:44 ` Eli Zaretskii
2023-08-17 18:52 ` Helmut Eller
2023-08-15 9:45 ` Richard Stallman
2023-08-10 2:15 ` Richard Stallman
2023-08-10 16:37 ` Jose E. Marchesi
2023-08-10 17:01 ` [External] : " Drew Adams
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87jzu4yioy.fsf@yahoo.com \
--to=luangruo@yahoo.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=rms@gnu.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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).