Newsgroups: comp.lang.lisp
Path: cantaloupe.srv.cs.cmu.edu!rochester!udel!news.mathworks.com!fu-berlin.de!news.dfn.de!news.dkrz.de!news.rrz.uni-hamburg.de!news.Hanse.DE!wavehh.hanse.de!cracauer
From: cracauer@wavehh.hanse.de (Martin Cracauer)
Subject: Re: CMUCL "save-lisp"
Message-ID: <1996May9.104346.27898@wavehh.hanse.de>
Organization: BSD User Group Hamburg
References: <4m64qv$q0j@bird.cs.ucsb.edu> <1996May5.171856.25036@wavehh.hanse.de> <4mnris$is3@bird.cs.ucsb.edu>
Date: Thu, 9 May 96 10:43:46 GMT
Lines: 59

mcguire@cs.ucsb.edu (Hugh W. Mcguire) writes:

>In article <1996May5.171856.25036@wavehh.hanse.de>,
>Martin Cracauer <cracauer@wavehh.hanse.de> wrote:
>+>mcguire@cs.ucsb.edu (Hugh W. Mcguire) writes:
>+>
>+>>I'm trying to save a lisp-image for fast later restarting of work, but I'm
>+>>encountering difficulties.
>+>
>+>>[...]
>+>
>+>>    % lisp -core=lcore
>+>                 ^
>+>                 ^
>+>
>+>Try `lisp -core lcore` (without '='). CMU CL doesn't give an error
>+>message when an invalid command line argument is given. Your invalid
>+>argument is being ignored and the normal Lisp image loaded. In Unix
>+>you can check for such effects with `ls -lu` on the cores file and you
>+>can see which file actually has been read by the Lisp process.
>+>
>+>Martin
>+>-- 
>+>%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
>+>Martin Cracauer <cracauer@wavehh.hanse.de>  -  BSD User Group Hamburg
>+>BSD, Lisp and other programming info http://www.bik-gmbh.de/~cracauer

>When I try without the "=":

>    % lisp -core lcore

>I get the following:

>    Warning:  #<Command Line Switch "core lcore"> is an illegal switch

Ah. So what happens is that you don't pass two parameters. You pass
one parameter with a blank inside it as if you typed 
lisp '-core lcore'

So, you either 
- typed something else than you wrote here
- have a broken shell
- this is a solaris-port specific problem.
- 'lisp' is really not the lisp binary, but a shell script or an
  alias where someone called 
     /usr/local/lib/cmucl/bin/lisp "$*"   
  or something like this that passes all parameters to the shell
  script as one big parameter.

I assume the latter is the reason. Have a look at what ever 'lisp' is
that appears in your path (or aliases, maybe in /etc/*) and see if
passes arguments correct. If you can't fix it this way, let me know,
I'll have a solaris machine to test this next week.

Martin
-- 
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
Martin Cracauer <cracauer@wavehh.hanse.de>  -  BSD User Group Hamburg
BSD, Lisp and other programming info http://www.bik-gmbh.de/~cracauer
