axiom-developer
[Top][All Lists]
Advanced

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

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


From: Gabriel Dos Reis
Subject: RE: [Axiom-developer] Axiom/GCL on windows
Date: Fri, 29 Dec 2006 19:56:08 -0600 (CST)

On Fri, 29 Dec 2006, Page, Bill wrote:

| 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)

I have not tested the build on Windows with the recen changes -- only
linux boxes.

| -------
|
| 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"))'

Nice detective work.

-- Gaby




reply via email to

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