From: Stefan Monnier <monnier@iro.umontreal.ca>
To: David Kuehling <dvdkhlng@gmx.de>
Cc: emacs-devel@gnu.org
Subject: Re: Some OpenWrt port related problems
Date: Tue, 28 Dec 2010 14:36:39 -0500 [thread overview]
Message-ID: <jwvr5d1lmo6.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87sjxi5hko.fsf@snail.Pool> (David Kuehling's message of "Tue, 28 Dec 2010 11:15:35 +0100")
> OpenWrt packages use cross-compilation, so Emacs is used in a NO_DUMP
> configuration, loading loadup.el every time it starts.
That's unfortunate, as this is completely untested and unsupported.
I expect you'll bump into further problems. Maybe a "simpler" solution
is to setup a simulation environment where you could perform the dump.
> This causes at least one problem with environment variables, that
> I already fixed [3].
Not sure if that's the right fix, but indeed there's a bug there that
shows up when using NO_DUMP. Make sure you record it via M-x
report-emacs-bug.
> Now I'm hitting another problem when using org-mode:
> File mode specification error:
> (wrong-type-argument stringp (require . t-mouse))
> After some debugging this looks like being caused by variable
> load-history containing the element:
> ((require . t-mouse))
> This looks a little broken, since all other elements have a
> filename-string in front of that cons cell, e.g.:
That one doesn't remind me of anything.
> Anybody knows who's fault that error is anyways?
I don't.
> is ((require . t-mouse)) a valid entry?
No.
> Is eval-after-load broken?
Not that I know.
> How does that entry get inserted into load-history in the first place?
That's the question, yes. But no, I have no idea how this can happen.
Stefan
next prev parent reply other threads:[~2010-12-28 19:36 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 [this message]
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
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
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=jwvr5d1lmo6.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--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 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).