all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: emacs-devel@gnu.org
Subject: Re: RFC: Cross compiling Emacs with qemu-user
Date: Tue, 12 Dec 2017 15:34:20 -0500	[thread overview]
Message-ID: <jwvk1xrsnfc.fsf-monnier+gmane.emacs.devel@gnu.org> (raw)
In-Reply-To: 87mv2nc0nj.fsf@home.blind.guru

> * In principle, would this be something Emacs would want to support?

I';ll let Eli and John chime in, but I don't see any reason why not.

> * What would need to be done to make the patch below acceptable?

Good question.  Some comments below.

>  EMACS = ${top_builddir}/src/emacs
> -emacs = EMACSLOADPATH= "${EMACS}" -batch --no-site-file --no-site-lisp
> +emacs = EMACSLOADPATH= ${EMACS} -batch --no-site-file --no-site-lisp

I'm not sure if Emacs can be built currently in a directory whose full
name includes spaces, but it's something that *should* work.  The above
would break it AFAICT, so we need some other solution.

> +AC_ARG_WITH([emulator],[AS_HELP_STRING([--with-emulator=EMULATOR],
> +    [Emulator to use when executing target binaries])],
> +    EMULATOR="$withval"
> +    AC_SUBST(EMULATOR))

It'd be good to make the doc slightly more precise (i.e. clarify that
it specifies an actual *command* rather than just which kind of
emulator we want to use).

> -RUN_TEMACS = ./temacs
> +RUN_TEMACS = temacs

Why did you need to get rid of the "./"?  It's needed to tell the shell
not to search through $PATH but in the cwd instead.

> -	$(MAKE) -C ../admin/unidata all EMACS="../$(bootstrap_exe)"
> +	$(MAKE) -C ../admin/unidata all EMACS="$(EMULATOR) $(bootstrap_exe)"

Hmm... how will $(EMULATOR) know to look in ../ ?


        Stefan




  parent reply	other threads:[~2017-12-12 20:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-12 17:32 RFC: Cross compiling Emacs with qemu-user Mario Lang
2017-12-12 17:51 ` Andreas Schwab
2017-12-12 20:34 ` Stefan Monnier [this message]
2017-12-12 21:03   ` Mario Lang

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=jwvk1xrsnfc.fsf-monnier+gmane.emacs.devel@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=emacs-devel@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 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.