[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [Gcl-devel] defpackage non-compliant?
From: |
Mike Thomas |
Subject: |
RE: [Gcl-devel] defpackage non-compliant? |
Date: |
Thu, 26 Jun 2003 09:35:28 +1000 |
Hi Sam.
Welcome to GNU Common Lisp.
Paul asked you:
| > Did you build gcl with --enable-ansi?
You replied:
| I downloaded
| <ftp://ftp.gnu.org/pub/gnu/gcl/cvs/gcl_2.5.3.japi.20030603_mingw32.zip>
That package is not ANSI compatible. Rather it is the so called
"traditional" CLtL1 build. Having said that I believe that defpackage is in
a state of transition in the CLtL1 build driven partly by the needs of the
Axiom developers.
You also said:
| I cannot build gcl with mingw:
....
| MGCLDIR=`echo /cygdrive/d/gnu/gcl | sed -e 'sX^\([a-z]\):X/\1Xg'` ; \
| GCLDIR=`echo /cygdrive/d/gnu/gcl` ; \
....
| configured with options \"'--prefix=d:/gnu/gcl' '--enable-ansi'
| '--enable-notify=no' '--enable-tkconfig=d:/gnu/cygwin/usr/lib/'
| '--enable-tclconfig=d:/gnu/cygwin/usr/lib/' '--enable-japi=yes'\"
Apparently that is because because you used Cygwin to host the build. That
system is not supported - you need MSYS. Check out the instructions (CVS
readme.mingw) included at the end of this email on how to build GCL under
Windows.
I myself use MinGW32 gcc 3.2.1 to build GCL releases under MSYS.
If you want to build the ANSI version of GCL under Windows, be warned that
you will need to pay particular attention to the final paragraph before
typing "make".
Let me know if you have any trouble.
Cheers
Mike Thomas
===============================================
BUILDING NATIVE WIN32 GNU COMMON LISP FROM CVS
===============================================
The preferred build host system for the Mingw32 compiler is
MSYS. I use gcc version 3.2, but version 2.95 certainly works.
===============================================
BUILDING GCL USING MSYS AS THE HOST
===============================================
BUILD TOOLS
- Mingw32 Version 2 Windows native gcc:
http://www.mingw.org/
- MSYS Mingw build environment, including the MSYS DTK
http://www.mingw.org/
- Source code for GCL.
http://savannah.gnu.org/projects/gcl/
It is a good idea to keep up to date with Mingw32 and MSYS. There
are usually updates for various parts of these packages to be found
on the web site.
SHORT SETUP NOTES
- Install Mingw32 and MSYS using the instructions at those sites.
DETAILED SETUP NOTES
- Start by installing the latest version of MinGW2.exe.
- By looking at the dates and version numbers appended to the other
packages on the download page, get any versions of gcc 3.2, binutils,
mingw-runtime, and w32api that are later than the Mingw2 package.
- Go to the top level Mingw32 installation directory - the one in which you
can see "bin", "lib" etc
- Extract those other packages in that directory eg:
tar xzf rumpty-dumpty.tar.gz
- Remove the Mingw version of "make" from the bin directory - it has serious
bugs and will not work properly for most tasks including building GCL and
Maxima. We will be using the MSYS version.
- Get MSYS and install it - follow the instructions - subscribe to the
mailing list and read the archives.
- In the MSYS directory install the "msysDTK-1.0.0-alpha-1.tar.gz" package
which gives you cvs, ssh, rlogin, etc.
BUILDING
- Change to your GCL source directory eg:
cd /c/cvs/gcl
- You are now ready to configure GCL:
./configure --prefix="c:/gcl" > configure.log 2>&1
Change the prefix directory as required for your final installation path.
I find it helpful to redirect output from "configure" and "make" into log
files for debugging and checking.
- Check the log.
- Type:
make >& make.log
- The "saved_gcl.exe" should turn up eventually in the unixport directory.
You
can try it out directly by typing:
./unixport/saved_gcl.exe
at the command prompt.
- To install:
make install >& install.log
It is necessary to install GCL before building Maxima.
- The batch file "gclm.bat" can be used to make a Windows desktop
shortcut.
- BFD fasloading, Stratified Garbage Collection (SGC) 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 needs someone with knowledge of BFD and PE-COFF linking to
fix some problems with the BFD library.
- A PCL/ANSI build ("configure --enable-ansi") can be obtained by adding
"(si::use-fast-links nil)" to the end of the list of commands in the SETUP
makefile macro in "pcl/makefile". I don't know why this is necessary on
Windows.
- [Gcl-devel] defpackage non-compliant?, Sam Steingold, 2003/06/24
- Re: [Gcl-devel] defpackage non-compliant?, Paul F. Dietz, 2003/06/24
- Re: [Gcl-devel] defpackage non-compliant?, Sam Steingold, 2003/06/25
- RE: [Gcl-devel] defpackage non-compliant?,
Mike Thomas <=
- Re: [Gcl-devel] defpackage non-compliant?, Sam Steingold, 2003/06/26
- RE: [Gcl-devel] defpackage non-compliant?, Mike Thomas, 2003/06/26
- Re: [Gcl-devel] defpackage non-compliant?, Sam Steingold, 2003/06/27
- RE: [Gcl-devel] defpackage non-compliant?, Mike Thomas, 2003/06/29
- Re: [Gcl-devel] defpackage non-compliant?, Sam Steingold, 2003/06/30
- RE: [Gcl-devel] defpackage non-compliant?, Mike Thomas, 2003/06/30