[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Gcl-devel] Re: (Summary view of above)

From: Dennis Decker Jensen
Subject: [Gcl-devel] Re: (Summary view of above)
Date: Fri, 16 Apr 2004 17:04:42 +0000

        Chris Hall wrote on 16 Apr 2004 04:07:54 -1000:

        Build process: it seems to me, as a new 'customer'
        of GCL, that it might make sense to --enable-ansi by
        default, esp. since ILISP only seems to work with the
        ANSI build.  If people want faster, smaller builds,
        then they should --disable-ansi.

I think it is already.  What version of Debian are you using?

If you do

$ export GCL_ANSI=yes


% setenv GCL_ANSI yes

in your favourite shell, then you should be all ready and
rolling ANSI.  If you look in /usr/lib/gcl-2.6.1/unixport
(or gcl-2.7.0 if using gclcvs dpkg) you should see two images,
one for CLtL1 (saved_gcl) and for ANSI (saved_ansi_gcl).
        ANSI/non-ANSI toggling: does the ANSI build revert to
        CLtL1 based on $GCL_ANSI?  Or should I have the non-ANSI
        saved_gcl available as well?

See above.  They are both there.  Just set GCL_ANSI environment var.
        ILISP: I'm not clear if --enable-ansi was required
        to make ILISP work, but I think it might be due
        to the different default package names, i.e. USER
        vs. COMMON-LISP-USER.  I couldn't figure out how to
        run an init script and change the GCL's active package
        when ILISP started it, though I see now that the shell
        script /usr/local/bin/gcl has an example.

On startup GCL will run `init.lsp' if there is one.

        Does anyone know of a workaround for the SETF

Camm has asked me to remind him to do something about logical
as well as physical pathnames in 2.7.0; in 2.6.2 coming soon
there will still be CLtL1 like pathnames that are incompatible
with ANSI.  This also prevents use of DEFSYSTEM and a number
of packages (dpkg) for common-lisp implementations made available
through common-lisp-controller (dpkg).  The jury is still out
on wheither how important this is for GCL.

Congratulations on getting ILISP to work with GCL!  Have you
tried SLIME?  GCL has a dbl-mode for debugging you might be
interested to play with and that needs a loving hand from
somebody knowing both elisp as well as GCL.

Dennis Decker Jensen

Good judgement comes from experience.
Experience comes from bad judgement.
 -- The Murphy's Law Calendar, ~1987

reply via email to

[Prev in Thread] Current Thread [Next in Thread]