RE: [Axiom-developer] Axiom/GCL on windows

[Page, Bill]

Gaby, Camm,

The most recent revision of build-improvements seems to
demonstrate a bug in gcl-2.6.8pre on Windows. The following
command generated a lisp error:

$ cd src/boot
$ ./../..//build/i686-pc-mingw32/bin/lisp.exe -batch -eval '(progn
(mapcar (function (lambda (x) (load x))) (quote ( "boothdr.o"
"exports.o"  "npextras.o"  "stage0/ptyout.o"  "stage0/btincl2.o"
"stage0/btscan2.o"  "stage0/typrops.o"  "
stage0/btpile2.o"  "stage0/typars.o"  "stage0/tytree1.o")))
(system::save-system "bootsys.exe"))'

Error: Unexpected end of #<string-input stream from "(progn (mapcar
(...">.
Fast links are on: do (si::use-fast-links nil) for debugging
Error signalled by SYSTEM:TOP-LEVEL.
Broken at SYSTEM:TOP-LEVEL.  Type :H for Help.
>>(quit)

-------

This works however if read via stdin.

$ echo '(progn (mapcar (function (lambda (x) (load x))) (quote (
"boothdr.o"  "exports.o"  "npextras.o"  "stage0/ptyout.o"
"stage0/btincl2.o"  "stage0/btscan2.o"  "stage0/typrops.o"
"stage0/btpile2.o"  "stage0/typars.o"  "stage0/tytree1.o")))
(system::save-system "bootsys.exe"))' |
./../..//build/i686-pc-mingw32/bin/lisp.exe

And it also works when replacing the unix / path separator with
the Windows \ path separator.

$ ./../..//build/i686-pc-mingw32/bin/lisp.exe -batch -eval '(progn
(mapcar (function (lambda (x) (load x))) (quote ( "boothdr.o"
"exports.o"  "npextras.o"  "stage0\\ptyout.o"  "stage0\\btincl2.o"
"stage0\\btscan2.o"  "stage0\\typrops.o
"  "stage0\\btpile2.o"  "stage0\\typars.o"  "stage0\\tytree1.o")))
(system::save-system "bootsys.exe"))'
Dumping from
C:/msys/1.0/home/bpage/axiom.test/build/i686-pc-mingw32/bin/lisp.exe
          to bootsys.exe
Copying executable up to data section...
        0x00000000 Offset in input file.
        0x00000000 Offset in output file.
        0x00136600 Size in bytes.
Dumping .data section...
        0x00538000 Address in process.
        0x00136600 Offset in output file.
        0x00009fa0 Size in bytes.
Copying rest of executable...
        0x001405a0 Offset in input file.
        0x001405a0 Offset in output file.
        0x00304d00 Size in bytes.
Dumping heap into executable...
        0x10100000 Heap start in process.
        0x00450000 Heap offset in executable.
        0x001b0000 Heap size in bytes.
Dumping .bss into executable...
        0x00553020 BSS start in process.
        0x00600000 BSS offset in executable.
        0x001152a0 BSS size in bytes.

---------

Perhaps there is something missing in the lisp reader
that evaluations the -eval string on Windows?

Regards,
Bill Page.