unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Glenn Morris <gmorris+news@ast.cam.ac.uk>
Subject: Re: emacs on freebsd, space limitation
Date: Fri, 22 Apr 2005 17:25:43 +0100	[thread overview]
Message-ID: <g4oec6hj7c.fsf@xpc14.ast.cam.ac.uk> (raw)
In-Reply-To: mailman.2181.1114012675.2895.help-gnu-emacs@gnu.org

Angelina Carlton wrote:

[ Emacs in under 50 MB? ]


A) If you have access to another machine running the same OS, or if
you have temp space in which you can build, then it's easy.

Configure and make in the normal way. Then before running `make
install-strip', delete all the .el files that have .elc counterparts:

for f in `find lisp -name "*.elc"`; do
    rm ${f%c}    # bash shell syntax
done


If you then do `make install-strip', the installed version uses 36MB.


B) If you can't use A), here is an ugly method that works. Someone who
understands the build process better (ie at all) could probably
suggest something more elegant. This needs a full 50MB, so transfer
all other files out of the way first.

1. On some other machine, untar emacs-21.4a source. 70MB, ack!

2. Delete a bunch of stuff you can live without:

for f in `find lisp -name "*.elc"`; do
    rm ${f%c}    # bash shell syntax
done

find . -name "ChangeLog*" -exec rm '{}' ';'

rm -rf nt msdos vms mac

3. Now down to 46MB, but need more space to build, so have to get rid of
some other stuff that it would be nice to keep:

rm -rf etc/* man/*.tex* info

4. Find some way to get size of lisp directory down to ~ 13MB. Eg:
cd lisp
rm -rf gnus obsolete play mail calendar eshell emulation net toolbar

Actually, rather than deleting these, you can move them somewhere else
and transfer them to the build machine later if you want them.

5. Now at ~ 25 MB, transfer to build machine.

6. ./configure
make src

49 MB, phew!

7. Tidy up a bit:

find . -name "*.[cho]" -exec rm '{}' ';'
( cd etc; ln -f DOC-21.4.1 DOC )
strip src/emacs

Leaves 26 MB. Run it as ./src/emacs (ignoring complaints), don't try
installing it.

At this point, you can move back some of the files from step 4, if you
want them.


C) Insult the sysadmin's (wo)manhood for failing to provide emacs on
the system.

D) alt.religion.emacs can probably supply a mob with pitchforks and
torches to help "persuade" the syadmin to install emacs.

  parent reply	other threads:[~2005-04-22 16:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.2181.1114012675.2895.help-gnu-emacs@gnu.org>
2005-04-20 16:16 ` emacs on freebsd, space limitation Pascal Bourguignon
2005-04-20 16:40   ` Joe Corneli
2005-04-20 16:54     ` Angelina Carlton
2005-04-20 17:45       ` Joe Corneli
     [not found]       ` <mailman.2202.1114019512.2895.help-gnu-emacs@gnu.org>
2005-04-20 18:04         ` Henrik Enberg
2005-04-20 19:07           ` Angelina Carlton
2005-04-20 16:59   ` Angelina Carlton
2005-04-22 16:25 ` Glenn Morris [this message]
2005-04-22 18:48   ` Angelina Carlton
2005-04-20 15:54 Angelina Carlton

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=g4oec6hj7c.fsf@xpc14.ast.cam.ac.uk \
    --to=gmorris+news@ast.cam.ac.uk \
    /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.
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).