From: Ken Raeburn <raeburn@raeburn.org>
To: David Kuehling <dvdkhlng@gmx.de>
Cc: Emacs Dev <emacs-devel@gnu.org>
Subject: Re: Some OpenWrt port related problems
Date: Wed, 29 Dec 2010 23:08:09 -0500 [thread overview]
Message-ID: <66798668-5808-473B-BF11-DF4DBA5464A1@raeburn.org> (raw)
In-Reply-To: <87pqsl7wt7.fsf@snail.Pool>
On Dec 29, 2010, at 04:28, David Kuehling wrote:
>>>>>> "Richard" == Richard Stallman <rms@gnu.org> writes:
>
>> Why do you want to avoid dumping?
>
> Because OpenWrt is using cross-compilation for everything. I.e. the
> system used for compilation is usually an x86 system, but the generated
> executables are for MIPS32 (when compiling for NanoNote).
>
> I could dump Emacs in the target system, from a wrapper script, when
> launched for the first time. But last time I tried that it failed with
> insufficient memory (32Mb RAM, no swap), so I'm going without dumping
> for now.
It sounds like running Emacs on such a system is going to be pretty marginal in any case, but do you recall what part of it failed? Finding the doc strings? The actual dumping?
Ken
next prev parent reply other threads:[~2010-12-30 4:08 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-28 10:15 Some OpenWrt port related problems David Kuehling
2010-12-28 19:36 ` Stefan Monnier
2010-12-28 21:12 ` David Kuehling
2010-12-28 22:02 ` Stefan Monnier
2010-12-29 9:37 ` David Kuehling
2010-12-29 7:47 ` Richard Stallman
2010-12-29 9:28 ` David Kuehling
2010-12-30 4:08 ` Ken Raeburn [this message]
2011-01-01 14:20 ` David Kuehling
2011-01-01 15:06 ` Andreas Schwab
2011-01-01 15:34 ` Eli Zaretskii
2011-01-02 1:35 ` Ken Raeburn
2011-01-02 13:53 ` David Kuehling
2011-01-02 14:44 ` Stefan Monnier
2011-01-02 14:55 ` David Kuehling
2011-01-02 20:35 ` Ken Raeburn
2011-01-02 21:12 ` David Kuehling
2011-01-03 9:32 ` David Kuehling
2010-12-30 16:06 ` Richard Stallman
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=66798668-5808-473B-BF11-DF4DBA5464A1@raeburn.org \
--to=raeburn@raeburn.org \
--cc=dvdkhlng@gmx.de \
--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.