unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
To: Po Lu <luangruo@yahoo.com>
Cc: eliz@gnu.org, emacs-devel@gnu.org
Subject: Re: The 'cross' directory
Date: Sat, 12 Aug 2023 21:43:31 -0400	[thread overview]
Message-ID: <E1qV08h-0001n2-4N@fencepost.gnu.org> (raw)
In-Reply-To: <87jzu4yioy.fsf@yahoo.com> (message from Po Lu on Wed, 09 Aug 2023 11:54:05 +0800)

[[[ To any NSA and FBI agents reading my email: please consider    ]]]
[[[ whether defending the US Constitution against all enemies,     ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]

  > 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.

In the past, building Emacs was cleanly separated into building
`temacs' and then using it to dump.  We included .elc files in the tar
ball so that users did not need to compile any Lisp code unless they
changed Lisp source.  (Byte-compiling Lisp code was slow and the .elc
files were portable.)

So I think it should have worked to make `temacs' cross-compiling
and then run the rest on the target machine.  That should have been
easy because it did not need to compile or link any C code.

That may still be workable.  `make temacs' ought to work ok under
cross-compilation, and the rest could be done on the target machine
without a C compiler or linker if `make temacs' has done its job.

Does this work?

-- 
Dr Richard Stallman (https://stallman.org)
Chief GNUisance of the GNU Project (https://gnu.org)
Founder, Free Software Foundation (https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)





  reply	other threads:[~2023-08-13  1:43 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
2023-08-13  1:43       ` Richard Stallman [this message]
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=E1qV08h-0001n2-4N@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=luangruo@yahoo.com \
    /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).