From owner-freebsd-questions Sat May 11 05:32:50 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id FAA09493 for questions-outgoing; Sat, 11 May 1996 05:32:50 -0700 (PDT) Received: from relay-2.mail.demon.net (disperse.demon.co.uk [158.152.1.77]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id FAA09485 for ; Sat, 11 May 1996 05:32:46 -0700 (PDT) Received: from post.demon.co.uk ([158.152.1.72]) by relay-2.mail.demon.net id ab27096; 11 May 96 13:32 +0100 Received: from jraynard.demon.co.uk ([158.152.42.77]) by relay-3.mail.demon.net id aa12618; 11 May 96 13:31 +0100 Received: (from fqueries@localhost) by jraynard.demon.co.uk (8.6.12/8.6.12) id MAA18153; Sat, 11 May 1996 12:12:35 GMT Date: Sat, 11 May 1996 12:12:35 GMT From: James Raynard Message-Id: <199605111212.MAA18153@jraynard.demon.co.uk> To: amnuay@comnet.spu.ac.th CC: questions@freebsd.org In-reply-to: (message from amnuay muthitacharoen on Fri, 10 May 1996 09:19:07 -0700 (PDT)) Subject: Re: CLISP installation on FreeBSD-486 machine Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >>>>> amnuay muthitacharoen writes: > > After I untarred "clisp.tgz", then I installed as follow :- > > 1) cc lisp.a -L. -lreadline -ltermcap -o lisp.run > > which gave me "lisp.run" > > 2) lisp.run -M lispinit.mem > > this gave me an error as follow :- > > Cannot map memory to address 536870912 . errno = 9 > lisp.run: Not enough memory for Lisp. > My machine uses "Conner Pheripherals 1275MB-CFS1275A" disk drive. Is this > the problem that this CLISP cannot see more than 536,870,912 bytes ? It's not disk space it's looking for, it's virtual memory (RAM + swap). I think the real problem however is that there's something peculiar about the format of the lisp.run executable. On Unix, every binary executable has some data at the start of the file which tells how the operating system various things about it, including how much memory it's going to need. My guess is that there's something not right here and the operating system is being asked for 500MB for memory! This sort of thing sometimes happens with Lisp interpreters - a very minimal version is written in C, the installation program builds and runs it, loads it with lots of powerful Lisp code and then dumps this image to disk, which is then the interpreter executable (you've probably seen this happen if you've built Emacs from scratch). The problem is that it's very easy to get a bad executable if you're porting it to a different system and don't get it right. If it's any consolation, I had exactly the same problem when I tried to install clisp, but I didn't have any time to look into it. There's a clisp mailing list, which may be a better place to ask (extract from comp.lang.lisp FAQ):- There is a mailing list for users of CLISP. It is the proper forum for questions about CLISP, installation problems, bug reports, application packages etc. For information about the list and how to subscribe, send mail to listserv@ma2s2.mathematik.uni-karlsruhe.de, with the two lines help information clisp-list in the message body. Alternatively, there's a free LISP interpreter which is actually being developed on FreeBSD, based on CMU Common Lisp:- http://www.mv.com/users/pw/lisp/dl/CMUCL-FreeBSD.tar.gz