From: Christopher DeMarco <email@example.com>
To: Bill Raynor <firstname.lastname@example.org>
Subject: Re: are elc files portable?
Date: Fri, 16 Jan 2009 20:31:02 -0500 [thread overview]
Message-ID: <20090117013102.GA6248@owl.prv.maya.com> (raw)
On Fri, Jan 16, 2009 at 06:42:28PM -0600, Bill Raynor wrote:
> org-mode. Can I compile on one and port to the others? They are all intel
> boxes if that makes a difference. Installing on the macs is a breeze, but
Yes, you can move the emacs bytecode from one machine to another *IF*
the processor endianness is the same. So Intel <--> Intel is fine. I
don't know a little-endian architecture off the top of my head --
anybody out there? (and of course, I'd love to be corrected/clarified
as I'm not hardcore CS/CE).
Mohit and Rohit are twin brothers. Mohit is tall and burly and
works at Motorola; Rohit is short and wiry and works at Intel.
They are highly competitive but inseparable. Both working as
engineers at large chip manufacturers, they constantly annoy their
colleagues with their constant bickering about whether
big-Indianness is better than little-Indianness.
> XP is a pain, as I don't have cygwin installed there. The two macs are
But you don't *have* to compile the elisp for org-mode. Go ahead and
move the .el around and it'll work just the same. The lisp
interpreter in Emacs does the byte-compilation before executing
anyway; pre-compiling just makes things faster by skipping the
Christopher DeMarco <email@example.com>
prev parent reply other threads:[~2009-01-17 1:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-17 0:42 are elc files portable? Bill Raynor
2009-01-17 1:31 ` Christopher DeMarco [this message]
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).