unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Dan Nicolaescu <dann@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Toon Claes <toon@iotcl.net>,
	9192@debbugs.gnu.org, Andreas Schwab <schwab@linux-m68k.org>
Subject: bug#9192: Cross-compile for ARM
Date: Mon, 29 Aug 2011 23:38:46 -0400	[thread overview]
Message-ID: <yxqpqjn4lh5.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <jwv1ux36bk9.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Tue, 02 Aug 2011 12:21:40 -0400")

Stefan Monnier <monnier@iro.umontreal.ca> writes:

>> Is it a 'feature' or is it a bug?


BTW, the trunk should be a bit better now than the 23.x release in terms
of building.

> It's not a feature, but it's not a bug we find very important to fix.
> IOW I'd be happy to accept patches which make cross-compiling easier,
> but I won't write them myself and I would only accept them if they're
> clean enough.
>
> This said, I do remember someone posting on this list about a similar
> issue and making actual progress in this direction.  And if you want to
> try it, here are some things I know will need to be solved:
> - We build a few programs used only during compilation: prefix-args,

prefix-args has been removed from the trunk.

>   make-docfile, probably a few more (can't remember test-distrub, but
>   if we build such a thing, then it's most likely in the set as well).

We should just remove test-distrib.c ASAP, it doesn't seem that useful anymore.

>   You'll have to change the Makefile to compile those for the host
>   rather than for the target.
> - The Elisp files in lisp and leim need to be compiled by Emacs, so the
>   src/bootstrap-emacs should be built for the host rather than for
>   the target.
> - You'll either want to build without dumping (i.e. set CANNOT_DUMP), or

"temacs" now runs as expected, it should work better than setting
CANNOT_DUMP.
It starts up a bit slower, but it is just as usable as a dumped emacs
after that.

>   you'll want to split the dump step since it needs to be run on the
>   target (but in either case you can do the dump for src/bootstrap-emacs
>   since that runs on the host).  Builds using CANNOT_DUMP tend to have
>   various misfeatures because this is basically never used and hence
>   doesn't get much/any testing.
>
> Maybe the easiest way to approach the problem is to first do a normal
> build on the host (which builds src/bootstrap-emacs and compiles all the
> Elisp files), then "rm src/*.o", reconfigure for the target and compile
> src/temacs (and maybe afterwards do the `dump' on the target).






  reply	other threads:[~2011-08-30  3:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-28 18:53 bug#9192: Cross-compile for ARM Toon Claes
2011-07-28 21:13 ` Andreas Schwab
2011-07-29 16:44   ` Toon Claes
2011-08-02 16:21     ` Stefan Monnier
2011-08-30  3:38       ` Dan Nicolaescu [this message]
2024-01-10 11:11 ` bug#13479: Cross Compiling " Stefan Kangas
2024-01-10 11:44   ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-10 11:56     ` Stefan Kangas
2024-01-10 13:10       ` Toon Claes via Bug reports for GNU Emacs, the Swiss army knife of text editors

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=yxqpqjn4lh5.fsf@fencepost.gnu.org \
    --to=dann@gnu.org \
    --cc=9192@debbugs.gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=schwab@linux-m68k.org \
    --cc=toon@iotcl.net \
    /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).