[Gcl-devel] up-to-date setup instructions for Win32 GCL
From:
Donald Winiecki
Subject:
[Gcl-devel] up-to-date setup instructions for Win32 GCL
Date:
Fri, 25 May 2012 12:53:44 -0600
Hi,
It's about a year late but included below is the most up-to-date setup directions for Win32 GCL. This includes setting up and using a CVS client, and building Win32 GCL on a current WinXP, WinVista and Win7.
Next it's the regular docs.
Best,
_don
=============================================== 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.
----------------------------------------------------------------------------
** INSTALLING ON UP-TO-DATE WINDOWS XP, WINDOWS VISTA AND WINDOWS 7 ** ** (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.
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).
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):
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' > /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):
Change the prefix directory and directory to which the log is output as required for your desired final installation paths.
When configure is completed, enter the following command at the MinGW command line (the MSYS shell):
make &>c:/_cvs/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 &>c:/_cvs/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
===============================================