<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel about="http://blog.gmane.org/gmane.lisp.gcl.devel">
    <title>gmane.lisp.gcl.devel</title>
    <link>http://blog.gmane.org/gmane.lisp.gcl.devel</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.lisp.gcl.devel/7448"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.lisp.gcl.devel/7446"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.lisp.gcl.devel/7438"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.lisp.gcl.devel/7437"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.lisp.gcl.devel/7433"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.lisp.gcl.devel/7427"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.lisp.gcl.devel/7426"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.lisp.gcl.devel/7425"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.lisp.gcl.devel/7424"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.lisp.gcl.devel/7422"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.lisp.gcl.devel/7420"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.lisp.gcl.devel/7416"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.lisp.gcl.devel/7415"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.lisp.gcl.devel/7414"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.lisp.gcl.devel/7400"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.lisp.gcl.devel/7395"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.lisp.gcl.devel/7393"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.lisp.gcl.devel/7392"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.lisp.gcl.devel/7391"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.lisp.gcl.devel/7389"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://comments.gmane.org/gmane.lisp.gcl.devel/7448">
    <title>How to submit GCL patches</title>
    <link>http://comments.gmane.org/gmane.lisp.gcl.devel/7448</link>
    <description>Over the last month, I've submitted several patches to fix problems on
current Fedora systems.  While a short discussion followed a couple of
the patches, largely I've been met with silence.  How should I be
proceeding?  Should I be submitting the patches to the Savannah patch
tracker instead of sending them to this list?  I am absolutely ready
to discuss the problems these patches address, and how I came up with
the proposed solutions ... in what forum?

Incidentally, the "Debian package page" link on
http://www.gnu.org/software/gcl/ is broken.  The trailing ".html"
should be changed to "/" to fix it.

Also, what version of GCL should I be attempting to package for
Fedora: 2.6.7, or current CVS (which, I gather, is intended to become
2.7.0 some day)?  I've also seen mention of a "2.6.8pre".  What is
that?  Thanks,
</description>
    <dc:creator>Jerry James</dc:creator>
    <dc:date>2008-12-02T21:34:43</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.lisp.gcl.devel/7446">
    <title>Patch: LaTeX 2.09 -&gt; 2e</title>
    <link>http://comments.gmane.org/gmane.lisp.gcl.devel/7446</link>
    <description>This gets rid of modern LaTeX complaints about running in
compatibility mode when processing xgcl-2/dwdoc.tex.  There isn't
anything terribly fancy in that document, so the conversion was
straightforward.  It consisted of the following mappings:

- \documentstyle -&gt; \documentclass
- {\bf ...} -&gt; \textbf{...}
- {\tt ...} -&gt; \texttt{...}
- {\em ...} -&gt; \emph{...}

I also replaced a few length settings in the preamble with use of the
geometry package.
</description>
    <dc:creator>Jerry James</dc:creator>
    <dc:date>2008-11-26T03:25:25</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.lisp.gcl.devel/7438">
    <title>Patch: adapt to newer autoconf versions</title>
    <link>http://comments.gmane.org/gmane.lisp.gcl.devel/7438</link>
    <description>If autoconf 2.61 is used to process the current configure.in, it
produces a script containing illegal shell script syntax, causing a
script failure at runtime.  This is due to some obsolete autoconf
usages within configure.in.  This patch fully updates configure.in for
use by autoconf 2.61.  Let me explain a few bits of the patch.

I added AC_PROG_EGREP, because AC_EGREP_HEADER (formerly
AC_HEADER_EGREP) now expands to an expression that includes
"$(EGREP)", which isn't set unless AC_PROG_EGREP is run.

I added AC_GNU_SOURCE and a corresponding #undef in acconfig because
some math functions (e.g., isnormal) aren't defined unless _GNU_SOURCE
is defined.  There was already a workaround in the script for this,
but it broke in a couple of cases on my Fedora 9 machine.

I reordered a few statements to make the "checking ..." messages and
their corresponding results be on the same line.

Quite a few obsolete macros were converted to their new forms.

There were a number of cases of strings quoted with quote marks
instead of square brackets.

I replaced the checks for endianness and alloca with the now builtin
autoconf checks.

My editor didn't like all the lines with trailing whitespace nor
spaces in front of tab characters.  I finally got tired of it whining
at me and let it clean all that up, so there are a bunch of lines with
whitespace-only changes.
</description>
    <dc:creator>Jerry James</dc:creator>
    <dc:date>2008-11-20T16:19:18</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.lisp.gcl.devel/7437">
    <title>Patch: compile with newer system BFD libraries</title>
    <link>http://comments.gmane.org/gmane.lisp.gcl.devel/7437</link>
    <description>This patch detects whether a newer system BFD library is being used,
specifically one that requires an output BFD.  If so, it adds code to
set up a dummy output BFD.  This lets me compile successfully with the
Fedora 9 BFD library.

This patch requires regenerating the configure script with autoconf,
and also using autoheader to regenerate h/gclincl.h.in.
Unfortunately, autoconf 2.61 generates a configure script that will
not run successfully, due to some obsolete autoconf usages in the
current configure.in.  I'll send a patch to fix that in a moment.
</description>
    <dc:creator>Jerry James</dc:creator>
    <dc:date>2008-11-20T15:59:09</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.lisp.gcl.devel/7433">
    <title>LD_COMMAND for Linux</title>
    <link>http://comments.gmane.org/gmane.lisp.gcl.devel/7433</link>
    <description>I'm struggling to understand the definition of LD_COMMAND in
h/linux.h.  Currently, it generates a string as follows:

  ld -d -S -N -x -A %s -T %x %s %s -o %s

but Linux uses GNU ld, where:

  -A sets the architecture
  -T sets the linker script file

Neither of those make any sense in this definition.  I suspect these
are the BSD linker options, where:

  -A identifies a symbol file
  -T specifies the start of the text segment

The equivalents in GNU ld are -R and -e, respectively.  Also, GNU ld
expects a base 10 number as the argument to -e, but BSD's -T expects a
hex number; note the %x in the LD_COMMAND definition.  So I don't see
how this works at all on a Linux system.  Shouldn't the definition be:

  ld -d -S -N -x -R %s -e %d %s %s -o %s

?  Is the code that invokes LD_COMMAND never executed on a Linux box?
</description>
    <dc:creator>Jerry James</dc:creator>
    <dc:date>2008-11-11T22:25:55</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.lisp.gcl.devel/7427">
    <title>Build trouble</title>
    <link>http://comments.gmane.org/gmane.lisp.gcl.devel/7427</link>
    <description>Hi.

I've got a hard time compiling GCL-2.6.7 (Linux (Linux From Scratch),
DualCore, Gcc 4.2.3, Glibc 2.7). The build is stuck on a segfault, caused
by a buggy malloc, Gentoo bugtracking list dixit :

Building symbol table for /sources/gcl-2.6.7/unixport/raw_pre_gcl ..

Unrecoverable error: Segmentation violation..
/bin/sh: line 1: 13485
Abandon                 /sources/gcl-2.6.7/unixport/raw_pre_gcl /sources/gcl-2.6.7/unixport/
-libdir /sources/gcl-2.6.7/ &lt; foo make[1]: *** [saved_pre_gcl] Erreur 134
rm raw_pre_gcl make[1]: quittant le répertoire
« /sources/gcl-2.6.7/unixport » make: *** [unixport/saved_pre_gcl] Erreur
2

I don't quite understand all the workarounds provided by the Gentoo list,
as they are quite contradictory. Can someone help me compile this
package ? I need it badly for Maxima.

\bye

PS : it used to compile quite fine on my previous installation... But I
didn't write down the process, and now the hard drive is gone back to its
creator !


</description>
    <dc:creator>Nicolas FRANCOIS</dc:creator>
    <dc:date>2008-11-09T15:47:14</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.lisp.gcl.devel/7426">
    <title>Absolut Memory Limit</title>
    <link>http://comments.gmane.org/gmane.lisp.gcl.devel/7426</link>
    <description>Hello gcl list,

i'am checking large matrices with gcl (GCL (GNU Common Lisp)  2.6.8 CLtL1    
Dec  1 2007 20:28:22, on Kubuntu x86_64 2.6.24-21-generic, with 2GB RAM) 
and found that i cannot allocate more memory to gcl. The snippet works with 
an array size of 5000 (runtime approx 1.3 seconds).

What i see (or how i interpret it) is that the memory footprint for gcl is 
constantly 262144 pages.
I see a lot of GC for the relocatable pages when the array size is 10000 
(break into debugger after 4 minutes).

Even with various (si:allocate- ) calls when starting the script the total 
amount of 'maximum pages' stays at 262144.
I rechecked this on a Dual Quadcore with 16GB Ram it showes the same amount 
of 'maximum pages'.


What is the recommened way to expand memory for large arrays like this ?

Thanks for any pointer to more infos.
Rgards
Heiko

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
Plain gcl -&gt; (room):

   434/434    50.7%         CONS BIGNUM RATIO COMPLEX STRUCTURE
     7/45     85.1%         FIXNUM SHORT-FLOAT LONG-FLOAT CHARACTER 
RANDOM-STATE READTABLE SPICE
   155/736    85.9%         SYMBOL STREAM PATHNAME CCLOSURE CLOSURE
     1/2      23.9%         PACKAGE
     2/59     91.8%         ARRAY HASH-TABLE VECTOR BIT-VECTOR
    21/33     98.0%         CFUN CFDATA
    48/59     96.5%         SFUN STRING GFUN VFUN AFUN

   970/2215               1 contiguous (112 blocks)
       26214                hole
       10485   0.1%       1 relocatable

       668 pages for cells
     38337 total pages
    201530 pages available
     22277 pages in heap but not gc'd + pages needed for gc marking
    262144 maximum pages


Array size 5000:

 10000/10000   2.1%         CONS BIGNUM RATIO COMPLEX STRUCTURE
 29790/36903   8.9%       8 FIXNUM SHORT-FLOAT LONG-FLOAT CHARACTER 
RANDOM-STATE READTABLE SPICE
  2000/2000    6.6%         SYMBOL STREAM PATHNAME CCLOSURE CLOSURE
     1/2      23.9%         PACKAGE
  1000/1000    0.0%         ARRAY HASH-TABLE VECTOR BIT-VECTOR
  4000/4000    0.5%         CFUN CFDATA
  2000/2000    2.3%         SFUN STRING GFUN VFUN AFUN

   970/2215                 contiguous (141 blocks)
       11210                hole
       56600  86.3%       5 relocatable

     48791 pages for cells
    117571 total pages
     47391 pages available
     97182 pages in heap but not gc'd + pages needed for gc marking
    262144 maximum pages

Array size 10000 (break into debugger after 3min):

 10000/10000   2.0%       1 CONS BIGNUM RATIO COMPLEX STRUCTURE
  1000/1000    0.5%       1 FIXNUM SHORT-FLOAT LONG-FLOAT CHARACTER 
RANDOM-STATE READTABLE SPICE
  2000/2000    6.6%         SYMBOL STREAM PATHNAME CCLOSURE CLOSURE
     1/2      23.9%         PACKAGE
  1000/1000    0.0%         ARRAY HASH-TABLE VECTOR BIT-VECTOR
  4000/4000    0.5%         CFUN CFDATA
  2000/2000    2.2%         SFUN STRING GFUN VFUN AFUN

   970/2215                 contiguous (139 blocks)
       40000                hole
       94690   0.0%    5981 relocatable

     20001 pages for cells
    155661 total pages
         1 pages available
    106482 pages in heap but not gc'd + pages needed for gc marking
    262144 maximum pages

#########################################################
; Test snippet

(declaim (optimize (speed 3)(safety 0)))

(progn
  (si::allocate-relocatable-pages 10000 t)
  (si::allocate 'cons 10000 t)
  (si::allocate 'fixnum 1000 t)
  (si::allocate 'symbol 2000 t)
  (si::allocate 'array 1000 t)
  (si::allocate 'string 2000 t)
  (si::allocate 'cfun 4000 t)

  ;; It is not recommended to make hole size less than 1000
  (si::set-hole-size 40000)

  (si::allocate-growth 'cons 1 10000 66 33)
  (si::allocate-growth 'fixnum 1 10000 66 33)
  (si::allocate-growth 'symbol 1 10000 66 33)
  (si::allocate-growth 'package 1 10000 66 33)
  (si::allocate-growth 'array 1 10000 66 33)
  (si::allocate-growth 'string 1 10000 66 33)
  (si::allocate-growth 'cfun 1 10000 66 33)
  (si::allocate-growth 'sfun 1 10000 66 33)
  (si::allocate-growth 'relocatable 1 10000 66 33)
  (si::allocate-growth 'contiguous 1 10000 66 33))

(defparameter arr (make-array '(10000 10000)
      :element-type 'single-float
      :initial-element 1.0))

(defun summe-elt (a)
"Just do some silly ops on array"
  (declare (type (simple-array single-float (10000 10000)) a))
  (let ((sum 0.0)
(wert 0.0)
(counter 0))
    (declare (type single-float sum wert))
    (dotimes (r 10000)
      (dotimes (c 10000)
(setf (aref a r c) wert)
(setf sum (the single-float (+ sum 1.0)))
(setf wert (the single-float (+ 1.0 wert)))
(setf counter (the integer (1+ counter)))))
    counter))

(time (format t "My GCL array ops counter: ~A~%" (summe-elt arr)))

############################################################
</description>
    <dc:creator>Heiko Schroeter</dc:creator>
    <dc:date>2008-11-06T12:26:46</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.lisp.gcl.devel/7425">
    <title>Patch for ~username code</title>
    <link>http://comments.gmane.org/gmane.lisp.gcl.devel/7425</link>
    <description>This is another patch against 2.6.7 + the current Debian patch.  This
one does a couple of minor cleanups to the code that handles filenames
starting with "~username".  First, such names may be greater than 20
characters long, so this code may overflow its buffer.  On Fedora,
they can be 256 characters long.  The patch uses LOGIN_NAME_MAX
instead.  Second, the variable "q" is initialized twice with the same
value, so this patch removes the second initialization.  Finally,
since we already know that q[0] == '~', there is no point in starting
the loop at index 0.  Starting it at index 1 also gets gcc to stop
whining about a possibly negative array index when setting name[n - 1]
to zero.

Regards,
</description>
    <dc:creator>Jerry James</dc:creator>
    <dc:date>2008-11-05T14:12:26</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.lisp.gcl.devel/7424">
    <title>Patch: minor Linux changes</title>
    <link>http://comments.gmane.org/gmane.lisp.gcl.devel/7424</link>
    <description>Here is a patch against 2.6.7 + the current Debian patch.  The first
hunk, against h/linux.h, makes the code use sigprocmask instead of
sigblock.  The sigprocmask interface has been available since Linux
kernel version 2.2 (current version is 2.6).  The sigblock interface
is currently deprecated.

The second hunk, against o/run_process.c, does two things.  First, it
uses dup2 instead of dup.  There's no particular problem here, it just
makes me nervous not to ask for the file descriptor we assume we got
later.  Second, it closes the fdin and fdout file descriptors, which
are no longer needed.

The next two hunks, against o/unixfsys.c, fixes a problem I am having
on Fedora 9, where at high optimization levels, the glibc headers
specify inline versions of some functions.  I'm getting calls made to
getwd() somehow, even though getcwd() is available.  I don't
understand it, but this part of the patch fixes the problem for me.
Also note that the getcwd prototype (in the #ifndef _WIN32 block) is
unnecessary, since getcwd is declared in unistd.h, which this file
#includes.

The last hunk, also against o/unixfsys.c, gets rid of a shell
invocation and a context switch just to change the name of a file.

Regards,
</description>
    <dc:creator>Jerry James</dc:creator>
    <dc:date>2008-11-04T22:08:34</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.lisp.gcl.devel/7422">
    <title>Patch: don't #include inside a function</title>
    <link>http://comments.gmane.org/gmane.lisp.gcl.devel/7422</link>
    <description>I'm taking over maintainership of the Fedora GCL package, effective
today.  I've grabbed the current Debian patch.  Even with that patch,
I'm getting a build failure, due to h/unrandomize.h.  Essentially, it
is not possible to #include &lt;unistd.h&gt; inside a function when
compiling with both optimization and -D_FORTIFY_SOURCE.  When I
complained about this to the glibc maintainers, they replied:

  Then GCL is buggy.  Standard headers are never meant to be included
  inside of a function.  E.g. ISO C99 says in 7.1.2/4:
  ... "If used, a header shall be included outside of any external
declaration or
  definition, and it shall first be included before the first
reference to any of
  the functions or objects it declares, or to any of the types or macros it
  defines."...

So here is a patch to move the #include statements out of functions.
After applying this patch, configure will need to be regenerated.

diff -dur gcl-2.6.7.ORIG/configure.in gcl-2.6.7/configure.in
--- gcl-2.6.7.ORIG/configure.in2008-11-03 16:58:14.000000000 -0700
+++ gcl-2.6.7/configure.in2008-11-04 08:58:03.000000000 -0700
&lt; at &gt;&lt; at &gt; -1032,7 +1032,11 &lt; at &gt;&lt; at &gt;
 fi

 AC_MSG_CHECKING([for personality(ADDR_NO_RANDOMIZE) support])
-AC_TRY_RUN([void gprof_cleanup() {};
+AC_TRY_RUN([#include &lt;sys/personality.h&gt;
+    #include &lt;syscall.h&gt;
+    #include &lt;unistd.h&gt;
+    #include &lt;alloca.h&gt;
+    void gprof_cleanup() {};
     int main(int argc,char *argv[],char *envp[]) {
             #include "h/unrandomize.h"
     return 0;}],CAN_UNRANDOMIZE_SBRK=1,CAN_UNRANDOMIZE_SBRK=0,CAN_UNRANDOMIZE_SBRK=0)
diff -dur gcl-2.6.7.ORIG/h/unrandomize.h gcl-2.6.7/h/unrandomize.h
--- gcl-2.6.7.ORIG/h/unrandomize.h2008-11-03 16:58:16.000000000 -0700
+++ gcl-2.6.7/h/unrandomize.h2008-11-04 08:58:24.000000000 -0700
&lt; at &gt;&lt; at &gt; -1,8 +1,3 &lt; at &gt;&lt; at &gt;
-#include &lt;sys/personality.h&gt;
-#include &lt;syscall.h&gt;
-#include &lt;unistd.h&gt;
-#include &lt;alloca.h&gt;
-
 {

   long pers = personality(0xffffffffUL);
diff -dur gcl-2.6.7.ORIG/o/main.c gcl-2.6.7/o/main.c
--- gcl-2.6.7.ORIG/o/main.c2008-11-03 16:58:56.000000000 -0700
+++ gcl-2.6.7/o/main.c2008-11-04 09:00:38.000000000 -0700
&lt; at &gt;&lt; at &gt; -27,6 +27,11 &lt; at &gt;&lt; at &gt;
 #include &lt;stdlib.h&gt;
 #include &lt;unistd.h&gt;
 #include &lt;string.h&gt;
+#ifdef CAN_UNRANDOMIZE_SBRK
+#include &lt;sys/personality.h&gt;
+#include &lt;syscall.h&gt;
+#include &lt;alloca.h&gt;
+#endif

 static void
 init_main(void);

Regards,
</description>
    <dc:creator>Jerry James</dc:creator>
    <dc:date>2008-11-04T16:04:46</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.lisp.gcl.devel/7420">
    <title>Signaling floating-point overflow?</title>
    <link>http://comments.gmane.org/gmane.lisp.gcl.devel/7420</link>
    <description>Does gcl signal an arithmetic-error on floating-point overflow?

I vaguely remember that it did, but my gcl 2.6.8 build (solaris) does
something and produces an error about printing a non-number.  I guess
that means an infinity was generated?

Can I make gcl produce an arithmetic-error on FP overflow?

Ray
</description>
    <dc:creator>Raymond Toy</dc:creator>
    <dc:date>2008-10-31T04:42:10</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.lisp.gcl.devel/7416">
    <title>Compiling on Windows</title>
    <link>http://comments.gmane.org/gmane.lisp.gcl.devel/7416</link>
    <description>I have a GCL install on Windows that works fine in interpreter mode,
and I'm trying to get it to compile a program, i.e. via GCC. Google
finds the following suggested methods:

(compile-file "main.lisp":system-p t)
(compiler::link '("main.o" "libuser32.a") "main.exe")

Result:

Compiling main.lisp.
End of Pass 1.
End of Pass 2.
OPTIMIZE levels: Safety=0 (No runtime error checking), Space=0,
Speed=3
Finished compiling main.lisp.
'.' is not recognized as an internal or external command,
operable program or batch file.

C:\ayane&gt;dir *.exe
 Volume in drive C is OS
 Volume Serial Number is 0422-C2D0

 Directory of C:\ayane

29/10/2008  09:43           454,232 raw_main_map.exe
              1 File(s)        454,232 bytes
              0 Dir(s)  67,711,852,544 bytes free

C:\ayane&gt;raw_main_map.exe
Program too big to fit in memory

The other suggested method:

C:\ayane&gt;\PROGRA~1\GCL-2.6.6-ANSI\lib\gcl-2.6.6\unixport
\saved_ansi_gcl -compile
 main.lisp

Compiling main.lisp.
End of Pass 1.
End of Pass 2.
OPTIMIZE levels: Safety=0 (No runtime error checking), Space=0,
Speed=3
Finished compiling main.lisp.

C:\ayane&gt;gcc -o main.exe main.o \PROGRA~1\GCL-2.6.6-ANSI\mingw\lib
\libuser32.a
main.o(.text+0xb):main.c: undefined reference to `vs_base'
main.o(.text+0x17):main.c: undefined reference to `vs_limit'
main.o(.text+0x1d):main.c: undefined reference to `vs_top'
[a couple more screenfuls of undefined references]

In both cases, the problem isn't with the compiling step per se, but
with the linking. Any idea what I'm doing wrong or what the correct
procedure is?
</description>
    <dc:creator>Russell Wallace</dc:creator>
    <dc:date>2008-10-29T18:53:34</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.lisp.gcl.devel/7415">
    <title>wrong value for (float-sign -0.0)</title>
    <link>http://comments.gmane.org/gmane.lisp.gcl.devel/7415</link>
    <description>
Camm --

  On IEEE-754 platforms, GCL reports a wrong value the sign of -0.0

   &gt;*features*

   (:COMPILER :NUMLIB :SDEBUG :DEFPACKAGE :GNU-LD :UNEXEC :BFD
       :NATIVE-RELOC :READLINE :TRUNCATE_USE_C :CLX-LITTLE-ENDIAN :BSD
       :GNU :LINUX :X86_64 :SGC :IEEE-FLOATING-POINT :UNIX :GMP :GCL :AKCL
       :COMMON :KCL)

   &gt;(float-sign -0.0)

   1.0

The correct value is -1.0.  This affects both GCL-2.6.8pre and GCL-2.7.0.

</description>
    <dc:creator>Gabriel Dos Reis</dc:creator>
    <dc:date>2008-09-28T05:25:17</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.lisp.gcl.devel/7414">
    <title>[CfPart] Lisp50&lt; at &gt;OOPSLA</title>
    <link>http://comments.gmane.org/gmane.lisp.gcl.devel/7414</link>
    <description>Lisp50&lt; at &gt;OOPSLA
...celebrating the 50th birthday of Lisp at OOPSLA 2008

Monday, October 20, 2008
Nashville, Tennessee, USA
co-located with OOPSLA 2008
participation is free for all OOPSLA participants
registration for at least one conference day at OOPSLA is required

URL: http:www.lisp50.org
Feed: http://lisp50.blogspot.com


Invited Speakers

+ William Clinger, Northeastern University, USA
+ Pascal Costanza, Vrije Universiteit Brussel, Belgium
+ Richard Gabriel, IBM Research, USA
+ Rich Hickey, Independent Consultant, USA
+ Alan Kay, Viewpoints Research Institute, USA
+ Fritz Kunze, USA
+ Ora Lassila, Nokia Research Center, USA
+ John McCarthy, USA
+ Kent Pitman, PTC, USA
+ Guy Steele, Sun Microsystems Laboratories, USA
+ Herbert Stoyan, University of Erlangen, Germany
+ Warren Teitelman, Google Inc., USA
+ JonL White, USA

Titles, abstracts, biographies and schedule will be announced at the
Lisp50 webpage and blog in the coming days and weeks.


Abstract

In October 1958, John McCarthy published one in a series of reports
about his then ongoing effort for designing a new programming language
that would be especially suited for achieving artificial intelligence.
That report was the first one to use the name LISP for this new
programming language. 50 years later, Lisp is still in use. This year we
are celebrating Lisp's 50th birthday. OOPSLA 2008 is an excellent venue
for such a celebration, because object-oriented programming benefited
heavily from Lisp ideas and because OOPSLA 2008 takes place in October,
exactly 50 years after the name Lisp has been used publicly for the
first time. We will have talks by John McCarthy himself, and numerous
other influential Lispers from the past five decades. We will also take
a look at the next 50 years of Lisp.


Organizers

+ Pascal Costanza, Vrije Universiteit Brussel, Belgium
+ Richard Gabriel, IBM Research, Hawthorne, NY, USA
+ Robert Hirschfeld, Hasso-Plattner-Institut, Potsdam, Germany
+ Guy Steele, Sun Microsystems Laboratories, Burlington, MA, USA

Sponsored by ACM SIGPLAN

Supported by
+ IBM Research
+ LispWorks Ltd
+ Franz Inc.
+ Clozure Associates

</description>
    <dc:creator>Pascal Costanza</dc:creator>
    <dc:date>2008-09-18T18:53:54</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.lisp.gcl.devel/7400">
    <title>_gp_disp vs __gnu_local_gp</title>
    <link>http://comments.gmane.org/gmane.lisp.gcl.devel/7400</link>
    <description>Greetings!  gcc-4.3 outputs the latter in place of the former.  Are
they equivalent, i.e. is this a simple renaming?  Why the change?

Take care,

</description>
    <dc:creator>Camm Maguire</dc:creator>
    <dc:date>2008-08-01T18:20:45</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.lisp.gcl.devel/7395">
    <title>Can't build GCL on regular Linux box</title>
    <link>http://comments.gmane.org/gmane.lisp.gcl.devel/7395</link>
    <description>_______________________________________________
Gcl-devel mailing list
Gcl-devel&lt; at &gt;gnu.org
http://lists.gnu.org/mailman/listinfo/gcl-devel
</description>
    <dc:creator>Blake McBride</dc:creator>
    <dc:date>2008-07-31T22:26:24</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.lisp.gcl.devel/7393">
    <title>ansi tests</title>
    <link>http://comments.gmane.org/gmane.lisp.gcl.devel/7393</link>
    <description>Hi,
Paul Dietz does not answer, so, presumably,
he stopped maintaining the ansi tests.
is anyone working on them?
who do I report bugs?
Thanks
Sam
</description>
    <dc:creator>Sam Steingold</dc:creator>
    <dc:date>2008-07-21T15:50:28</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.lisp.gcl.devel/7392">
    <title>Updated directions for setting up MinGW and MSYS onMS-Vista (and other stuff)</title>
    <link>http://comments.gmane.org/gmane.lisp.gcl.devel/7392</link>
    <description>The following (and attached) is my update on the installation and setup
directions for TortoiseCVS, MinGW, MSYS and GCC for building GCL.  It
would be terrific if anyone using Vista could check this out for me and
let me know if it works for them.

Just something to add * I've now verified this with both GCL-2.6.7
and GCL-2.6.8pre (ANSI).  Though I should _also_ say that the process is
somewhat flaky on Vista; sometimes I have to checkout from the CVS
several times before I can successfully build the .exe.  There may be
something unusual going on in the checkout process with TortoiseCVS.  I
suspect this because, on installation, TortoiseCVS reports that it is
not fully compatible with MS-Vista.  Since I'm using the most recent
update of TortoiseCVS, I'll have to keep attentive of any developments
in that tool.

Best regards from under the beautiful and cloudless blue skies of
Boise, Idaho!

_don winiecki



*----------- the updated setup directions follow *----------- 


===============================================
BUILDING NATIVE WIN32 GNU COMMON LISP FROM CVS
===============================================

The preferred build host system for the Mingw32 compiler is MSYS.

I use gcc version 3.3.1 and binutils 2.14.90, but earlier versions
of gcc back to 2.95 are OK provided that you remove the
"-fno-zero-initialized-in-bss" flag in "h/mingw.defs" before running
"configure".

Note that gcc 3.3.3 and gcc 3.4.0 do NOT work; likewise binutils
2.13.90
and 2.15.90.

The working binutils version can be found at:

http://gd.tuwien.ac.at/gnu/mingw/binutils-2.14.90-20030612-1.tar.gz 

===============================================
INSTALL AND CONFIGURE TORTOISE CVS
===============================================

Download Tortoise CVS from:  http://www.tortoisecvs.org/ 

After downloading, install Tortoise CVS and included programs, 
accepting default installation directories.

===============================================
DOWNLOAD CVS FOR GCL
===============================================

Choose a directory to which you will download (check out) of the GCL
CVS
(I created c:\_cvs).

Enter the directory created and right click.  The context menu will
show
`CVS checkout' as a context menu itemu.

Choose the 'CVS checkout' context menu item.  You should be presented
with
a dialogue box titled 'TortoiseCVS-Checkout Module'.  

Under the 'Module' tab, enter the following:

For Protocol, enter

     :pserver

For `server', enter

    cvs.savannah.gnu.org     

For `Repository folder', enter

    /sources/gcl

For `User name', enter

     anonymous

On the right side of the dialog box, for `Module', enter

     gcl

Under the 'Revision' tab:

Select the 'Choose branch or tag' radio button

Select the 'Update list...' button

Open the 'Branch or tag name:' drop down list and select the version
you want
to build

Under the 'Options' tab:

Select the `Export - for making a software release' radio button

Check the `Use UNIX line ending' box

Choose the 'Enter your own folder name' radio button

In the 'Custom folder name:' field, enter the name of the folder you
desire
to be created (for example, 'gcl-2.6.7' to match the version to be
built)

Now, click again on `Module' tab. Click on OK.  You should see that
tortoise CVS is checking out GCL from CVS repo.


More information on CVS access is available here

   http://savannah.gnu.org/cvs/?group=gcl 


================================================
INSTALLING BUILD TOOLS (MinGW, MSYS)
================================================

------------------------------------------------
** IF INSTALLING ON WINDOWS XP **
** (see below if installing on WINDOWS VISTA) **
------------------------------------------------

BUILD TOOLS

Subject to the above warnings, it is usually a good idea to keep up to
date with Mingw32 and MSYS.  Updates for various parts of these
packages
are available on the web site.

Go to http://www.mingw.org/download.shtml and download

  http://prdownloads.sf.net/mingw/MinGW-3.1.0-1.exe?download 

  http://prdownloads.sf.net/mingw/MSYS-1.0.9.exe?download 

  http://prdownloads.sf.net/mingw/msysDTK-1.0.1.exe?download 

 
http://prdownloads.sf.net/mingw/gcc-core-3.3.1-20030804-1.tar.gz?download


Install these files in the same order as above. Accept the default 
locations. GCC-CORE-3.3.1-20038041.tar.gz' should be extracted into 
c:/mingw and overwrites the older version of gcc. 

When you are done, you should be able to start MSYS and a get the '$'
prompt
(customized for your machine name and your username, if active)

To check the installation, type 'gcc -v' at the prompt.  If all was
installed
properly you should see:

  gcc version 3.3.1 (mingw special 20030804-1)


------------------------------------------------
** IF INSTALLING ON WINDOWS VISTA **
** (see above if installing on WINDOWS XP) **
** (Thanks to Dan Raymond for this: **
**
http://readlist.com/lists/lists.sourceforge.net/mingw-msys/0/918.html)
**
------------------------------------------------

BUILD TOOLS

Subject to the above warnings, it is usually a good idea to keep up to
date with Mingw32 and MSYS.  Updates for various parts of these
packages
are available on the web site.

(Alternative location for these files is [as of 6 July 08]:
 http://www.mingw.org/download.shtml and download)

Install these files in the same order as indicated below.  Accept the 
default locations.

  http://prdownloads.sf.net/mingw/MinGW-3.1.0-1.exe?download 

When the following program opens a terminal window and asks permission
to 
perform postinstall processing, press `n' and `enter' to abort the 
postinstall processing (otherwise, an error may occur and Vista will 
generate over 100 windows).  

  http://prdownloads.sf.net/mingw/MSYS-1.0.10.exe?download 

  http://prdownloads.sf.net/mingw/msysDTK-1.0.1.exe?download 

Open an MSYS window and type the following command (this will allow you
to 
use the MSYS version of ftp instead of the Windows version of ftp 
subsequently):

mv /bin/ftp /bin/ftp.old 

Copy the following files to c:\mingw

 
http://prdownloads.sf.net/mingw/binutils-2.14.90-20030612-1.tar.gz?download


 
http://prdownloads.sf.net/mingw/gcc-core-3.3.1-20030804-1.tar.gz?download


  http://prdownloads.sf.net/mingw/mingw-runtime-3.14.tar.gz?download 

  http://prdownloads.sf.net/mingw/w32api-3.11.tar.gz?download 

Open an MSYS window and execute the following commands (The first four

command lines below untar the archives and delete them while the last
line 
sets up the mount point for mingw (you need to do this manually since
you 
aborted the post install for MSYS).

cd /c/mingw
gzip -d *.gz
find -name '*.tar' -exec tar -xvf {} \;
rm *.tar
echo 'C:/mingw /mingw' &gt; /etc/fstab


When you are done, you should be able to start MSYS and a get the '$'
prompt
(customized for your machine name and your username, if active).  

To check the installation, type 'gcc -v' at the prompt.  If all was
installed
properly you should see the following.  (If not, something got missed
along
the way.  At this point, uninstall msysDTK, MSYS and MinGW through
Windows' 
control panel and delete the c:\MinGW and c:\msys directories, reboot
and 
reinstall following the procedure above.)

  gcc version 3.3.1 (mingw special 20030804-1)

===============================================
BUILDING GCL USING MSYS AS THE HOST
===============================================

At the MSYS '$' prompt, change to your GCL source directory (for
example):

  cd /c/_cvs/gcl

You are now ready to configure GCL:

If you want to build the CLTL1 variant, type:

  ./configure --prefix="c:/gcl" &gt; configure.log 2&gt;&amp;1

If you want to build the ANSI variant, type:

  ./configure --prefix="c:/gcl" &gt; --enable-ansi configure.log 2&gt;&amp;1

  Change the prefix directory as required for your desired final
installation 
  path.

When configure is completed, enter the following command at the MinGW
command
line (the MSYS shell):

   make &gt;&amp; make.log

On my dual core 2.2GHz machine, the process takes about 10-12 minutes. 
The 
"saved_gcl.exe" (or "saved_ansi_gcl.exe") should turn up eventually in

the unixport directory (inside the \lib\gcl-x.x.x directory of the
final 
installation directory).  

You can try it out directly inside the MSYS shell by typing the
following at
the MSYS command prompt.


For the CLtL1 version, type the following: 

  ./unixport/saved_gcl.exe

For the ANSI version, type the following:

  ./unixport/saved_ansi_gcl.exe

To install, type the following at the MSYS command prompt:

  make install &gt;&amp; install.log

- The batch file "gclm.bat" can be used to make a Windows desktop 
  shortcut.  (NOTE: I have not been able to make this batch file work
[djw])

- BFD fasloading, Stratified Garbage Collection (SGC) readline and
GCL-TK 
  don't work under Windows.  The configuration options above provide a
  "traditional" GCL executable which will build the current CVS version
of
  Maxima.  The BFD option will depend on someone with knowledge of BFD
and 
  PE-COFF linking fixing some problems with the BFD library - I am
slowly
  absorbing the info needed, but we really need input from an expert. 
My
  inclination is to stick with custom relocation as BFD is less
efficient.

===============================================
INSTALLING GCL INFORMATION ACCESSIBLE FROM GCL INTERPRETER
===============================================

Download "gcl.info.tgz" from ftp://ftp.gnu.org/pub/gnu/gcl/ 

Make the following directory path and unpack the downloaded file into 

C:\usr\local\gnu\info

===============================================
RUNNING GCL
===============================================

You can move the final installation folder (for example,
"GCL-2.6.7-ANSI")
anywhere on your hard drive (typically, c:\program files).

Create a shortcut to the executable (either "saved_gcl.exe" or 
"saved_ansi_gcl.exe") and assign to it the icon located in the \bin
directory.

You can then move the shortcut to anywhere (the 'Start' menu or your
'Quick
Launch' menu).  Double click the icon to launch GCL.

===============================================
CONFIGURE GCL TO RUN IN INFERIOR MODE UNDER EMACS
=============================================== 

Follow directions provided by Gordon Novak Jr. at:

http://www.cs.utexas.edu/users/novak/gclwin.html 


=============================================== 
Original setup and configuration directions by Mike Thomas, 15 Jun
2004.

Updates and modifications by Don Winiecki, 1:06 PM 01 Jan 2008, using
details
provided by Mike Thomas, Camm Maguire, Gaby Dos Reis, and Gordon Novak
Jr.  
(http://lists.gnu.org/archive/html/axiom-developer/2003-10/msg00227.html)

Updates for setup on MS-Vista by Don Winiecki, 12:40PM 06 Jul 2008,
using
information provided by Dan Raymond.
===============================================
BUILDING NATIVE WIN32 GNU COMMON LISP FROM CVS
===============================================

The preferred build host system for the Mingw32 compiler is MSYS.

I use gcc version 3.3.1 and binutils 2.14.90, but earlier versions
of gcc back to 2.95 are OK provided that you remove the
"-fno-zero-initialized-in-bss" flag in "h/mingw.defs" before running
"configure".

Note that gcc 3.3.3 and gcc 3.4.0 do NOT work; likewise binutils 2.13.90
and 2.15.90.

The working binutils version can be found at:

http://gd.tuwien.ac.at/gnu/mingw/binutils-2.14.90-20030612-1.tar.gz

===============================================
INSTALL AND CONFIGURE TORTOISE CVS
===============================================

Download Tortoise CVS from:  http://www.tortoisecvs.org/

After downloading, install Tortoise CVS and included programs, 
accepting default installation directories.

===============================================
DOWNLOAD CVS FOR GCL
===============================================

Choose a directory to which you will download (check out) of the GCL CVS
(I created c:\_cvs).

Enter the directory created and right click.  The context menu will show
`CVS checkout' as a context menu itemu.

Choose the 'CVS checkout' context menu item.  You should be presented with
a dialogue box titled 'TortoiseCVS-Checkout Module'.  

Under the 'Module' tab, enter the following:

For Protocol, enter

     :pserver

For `server', enter

    cvs.savannah.gnu.org     

For `Repository folder', enter

    /sources/gcl

For `User name', enter

     anonymous

On the right side of the dialog box, for `Module', enter

     gcl

Under the 'Revision' tab:

Select the 'Choose branch or tag' radio button

Select the 'Update list...' button

Open the 'Branch or tag name:' drop down list and select the version you want
to build

Under the 'Options' tab:

Select the `Export - for making a software release' radio button

Check the `Use UNIX line ending' box

Choose the 'Enter your own folder name' radio button

In the 'Custom folder name:' field, enter the name of the folder you desire
to be created (for example, 'gcl-2.6.7' to match the version to be built)

Now, click again on `Module' tab. Click on OK.  You should see that
tortoise CVS is checking out GCL from CVS repo.


More information on CVS access is available here

   http://savannah.gnu.org/cvs/?group=gcl 


================================================
INSTALLING BUILD TOOLS (MinGW, MSYS)
================================================

------------------------------------------------
** IF INSTALLING ON WINDOWS XP **
** (see below if installing on WINDOWS VISTA) **
------------------------------------------------

BUILD TOOLS

Subject to the above warnings, it is usually a good idea to keep up to
date with Mingw32 and MSYS.  Updates for various parts of these packages
are available on the web site.

Go to http://www.mingw.org/download.shtml and download

  http://prdownloads.sf.net/mingw/MinGW-3.1.0-1.exe?download

  http://prdownloads.sf.net/mingw/MSYS-1.0.9.exe?download

  http://prdownloads.sf.net/mingw/msysDTK-1.0.1.exe?download

  http://prdownloads.sf.net/mingw/gcc-core-3.3.1-20030804-1.tar.gz?download

Install these files in the same order as above. Accept the default 
locations. GCC-CORE-3.3.1-20038041.tar.gz' should be extracted into 
c:/mingw and overwrites the older version of gcc. 

When you are done, you should be able to start MSYS and a get the '$' prompt
(customized for your machine name and your username, if active)

To check the installation, type 'gcc -v' at the prompt.  If all was installed
properly you should see:

  gcc version 3.3.1 (mingw special 20030804-1)


------------------------------------------------
** IF INSTALLING ON WINDOWS VISTA **
** (see above if installing on WINDOWS XP) **
** (Thanks to Dan Raymond for this: **
** http://readlist.com/lists/lists.sourceforge.net/mingw-msys/0/918.html) **
------------------------------------------------

BUILD TOOLS

Subject to the above warnings, it is usually a good idea to keep up to
date with Mingw32 and MSYS.  Updates for various parts of these packages
are available on the web site.

(Alternative location for these files is [as of 6 July 08]:
 http://www.mingw.org/download.shtml and download)

Install these files in the same order as indicated below.  Accept the 
default locations.

  http://prdownloads.sf.net/mingw/MinGW-3.1.0-1.exe?download

When the following program opens a terminal window and asks permission to 
perform postinstall processing, press `n' and `enter' to abort the 
postinstall processing (otherwise, an error may occur and Vista will 
generate over 100 windows).  

  http://prdownloads.sf.net/mingw/MSYS-1.0.10.exe?download

  http://prdownloads.sf.net/mingw/msysDTK-1.0.1.exe?download

Open an MSYS window and type the following command (this will allow you to 
use the MSYS version of ftp instead of the Windows version of ftp 
subsequently):

mv /bin/ftp /bin/ftp.old

Copy the following files to c:\mingw

  http://prdownloads.sf.net/mingw/binutils-2.14.90-20030612-1.tar.gz?download

  http://prdownloads.sf.net/mingw/gcc-core-3.3.1-20030804-1.tar.gz?download

  http://prdownloads.sf.net/mingw/mingw-runtime-3.14.tar.gz?download

  http://prdownloads.sf.net/mingw/w32api-3.11.tar.gz?download

Open an MSYS window and execute the following commands (The first four 
command lines below untar the archives and delete them while the last line 
sets up the mount point for mingw (you need to do this manually since you 
aborted the post install for MSYS).

cd /c/mingw
gzip -d *.gz
find -name '*.tar' -exec tar -xvf {} \;
rm *.tar
echo 'C:/mingw /mingw' &gt; /etc/fstab


When you are done, you should be able to start MSYS and a get the '$' prompt
(customized for your machine name and your username, if active).  

To check the installation, type 'gcc -v' at the prompt.  If all was installed
properly you should see the following.  (If not, something got missed along
the way.  At this point, uninstall msysDTK, MSYS and MinGW through Windows' 
control panel and delete the c:\MinGW and c:\msys directories, reboot and 
reinstall following the procedure above.)

  gcc version 3.3.1 (mingw special 20030804-1)

===============================================
BUILDING GCL USING MSYS AS THE HOST
===============================================

At the MSYS '$' prompt, change to your GCL source directory (for example):

  cd /c/_cvs/gcl

You are now ready to configure GCL:

If you want to build the CLTL1 variant, type:

  ./configure --prefix="c:/gcl" &gt; configure.log 2&gt;&amp;1

If you want to build the ANSI variant, type:

  ./configure --prefix="c:/gcl" &gt; --enable-ansi configure.log 2&gt;&amp;1

  Change the prefix directory as required for your desired final installation 
  path.

When configure is completed, enter the following command at the MinGW command
line (the MSYS shell):

   make &gt;&amp; make.log

On my dual core 2.2GHz machine, the process takes about 10-12 minutes.  The 
"saved_gcl.exe" (or "saved_ansi_gcl.exe") should turn up eventually in 
the unixport directory (inside the \lib\gcl-x.x.x directory of the final 
installation directory).  

You can try it out directly inside the MSYS shell by typing the following at
the MSYS command prompt.


For the CLtL1 version, type the following: 

  ./unixport/saved_gcl.exe

For the ANSI version, type the following:

  ./unixport/saved_ansi_gcl.exe

To install, type the following at the MSYS command prompt:

  make install &gt;&amp; install.log

- The batch file "gclm.bat" can be used to make a Windows desktop 
  shortcut.  (NOTE: I have not been able to make this batch file work [djw])

- BFD fasloading, Stratified Garbage Collection (SGC) readline and GCL-TK 
  don't work under Windows.  The configuration options above provide a
  "traditional" GCL executable which will build the current CVS version of
  Maxima.  The BFD option will depend on someone with knowledge of BFD and 
  PE-COFF linking fixing some problems with the BFD library - I am slowly
  absorbing the info needed, but we really need input from an expert.  My
  inclination is to stick with custom relocation as BFD is less efficient.

===============================================
INSTALLING GCL INFORMATION ACCESSIBLE FROM GCL INTERPRETER
===============================================

Download "gcl.info.tgz" from ftp://ftp.gnu.org/pub/gnu/gcl/

Make the following directory path and unpack the downloaded file into 

C:\usr\local\gnu\info

===============================================
RUNNING GCL
===============================================

You can move the final installation folder (for example, "GCL-2.6.7-ANSI")
anywhere on your hard drive (typically, c:\program files).

Create a shortcut to the executable (either "saved_gcl.exe" or 
"saved_ansi_gcl.exe") and assign to it the icon located in the \bin directory.

You can then move the shortcut to anywhere (the 'Start' menu or your 'Quick
Launch' menu).  Double click the icon to launch GCL.

===============================================
CONFIGURE GCL TO RUN IN INFERIOR MODE UNDER EMACS
=============================================== 

Follow directions provided by Gordon Novak Jr. at:

http://www.cs.utexas.edu/users/novak/gclwin.html


=============================================== 
Original setup and configuration directions by Mike Thomas, 15 Jun 2004.

Updates and modifications by Don Winiecki, 1:06 PM 01 Jan 2008, using details
provided by Mike Thomas, Camm Maguire, Gaby Dos Reis, and Gordon Novak Jr.  
(http://lists.gnu.org/archive/html/axiom-developer/2003-10/msg00227.html)

Updates for setup on MS-Vista by Don Winiecki, 12:40PM 06 Jul 2008, using
information provided by Dan Raymond._______________________________________________
Gcl-devel mailing list
Gcl-devel&lt; at &gt;gnu.org
http://lists.gnu.org/mailman/listinfo/gcl-devel
</description>
    <dc:creator>Donald Winiecki</dc:creator>
    <dc:date>2008-07-06T20:20:28</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.lisp.gcl.devel/7391">
    <title>Building GCL on MS-Vista</title>
    <link>http://comments.gmane.org/gmane.lisp.gcl.devel/7391</link>
    <description>Just to make an early announcement, I've managed to root out a few
disconnected sources that allowed me to successfully setup MinGW, MSYS
and GCC so I can build GCL on my new Vista box.  I've built gcl-2.6.8pre
in both ANSI and CLtL1 form under Vista and both seem to operate
properly through a few simple tests.

I'll be writing up the details in an update to the procedure I prepared
a few months ago and send that on to the list.  At that point it would
be good if anyone else with a Vista machine could try it out to make
sure it works more generally.

When I can, I'll get up to speed on how to insert it into the CVS for
broader distribution.

Best, 

_don winiecki
</description>
    <dc:creator>Donald Winiecki</dc:creator>
    <dc:date>2008-07-06T02:52:24</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.lisp.gcl.devel/7389">
    <title>Compiling GCL for Win32 under Vista</title>
    <link>http://comments.gmane.org/gmane.lisp.gcl.devel/7389</link>
    <description>I've just been handed a new computer running MS-Vista and have been
working today to get things set up to see if I could build GCL on it.

While I still have a few things in mind to try, it appears that the
same MSYS and MinGW configurations that allowed GCC to function under
XPsp2 won't work under Vista.  

It appears to be a memory allocation thing, which if the case, would be
well beyond my ability to address.  

If anyone has succeeded in setting up MinGW, MSYS and GCC, and gotten
GCL to compile under Vista I would be very happy to hear how you
installed and configured things!

Best, 

_don winiecki
</description>
    <dc:creator>Donald Winiecki</dc:creator>
    <dc:date>2008-07-02T23:49:56</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.lisp.gcl.devel/7385">
    <title>custom lisp code after save-system and GPL</title>
    <link>http://comments.gmane.org/gmane.lisp.gcl.devel/7385</link>
    <description>_______________________________________________
Gcl-devel mailing list
Gcl-devel&lt; at &gt;gnu.org
http://lists.gnu.org/mailman/listinfo/gcl-devel
</description>
    <dc:creator>Mykhaylo Sorochan</dc:creator>
    <dc:date>2008-04-17T14:44:44</dc:date>
  </item>
  <textinput about="http://search.gmane.org/?group=$group=gmane.lisp.gcl.devel">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.lisp.gcl.devel</link>
  </textinput>
</rdf:RDF>
