[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [Gcl-devel] ANSI Windows: in-package failure
From: |
Mike Thomas |
Subject: |
RE: [Gcl-devel] ANSI Windows: in-package failure |
Date: |
Fri, 20 Feb 2004 17:37:04 +1000 |
Hi again.
| OK, I just did something similar. Please test.
Works.
| OK, I think I've put in changes now that should let compiler::link
| work on mingw. Please test. Note that the firstfile and lastfile
| modules are shipped out in make install.
Noted, tested, passed, ANSI release candidate zip file for external testing
in the usual location.
I didn't have time for the usual Maxima/ACL2 builds today though.
I ran a compiler::linked executable with a GCL system call which gave me a
Lisp prompt inside a Lisp prompt:
(system (compiler::link nil "c:/foo"))
-------------------------------------------------------------------
...
Dumping .bss into executable...
0x00639000 BSS start in process.
0x006e0000 BSS offset in executable.
0x00116fe0 BSS size in bytes.
GCL (GNU Common Lisp) (2.6.1) Fri Feb 20 15:24:14 EAST 2004
Licensed under GNU Library General Public License
Modifications of this banner must retain notice of a compatible license
Dedicated to the memory of W. Schelter
Use (help) to get some basic information on how to use GCL.
>(system "dir c:/foo.exe")
Invalid switch - "foo.exe".
0
1
>(system "dir c:\\foo.exe")
Volume in drive C has no label.
Volume Serial Number is 44EE-D89E
Directory of c:\
20/02/2004 05:13 PM 8,351,712 foo.exe
1 File(s) 8,351,712 bytes
0 Dir(s) 14,194,020,352 bytes free
0
0
>(system "dir
c:\\Progra\~1\\GCL-2.6.1-ANSI\\lib\\gcl-2.6.1\\unixport\\saved_ans
i_gcl.exe")
Volume in drive C has no label.
Volume Serial Number is 44EE-D89E
Directory of c:\Progra~1\GCL-2.6.1-ANSI\lib\gcl-2.6.1\unixport
20/02/2004 05:12 PM 18,771,648 saved_ansi_gcl.exe
1 File(s) 18,771,648 bytes
0 Dir(s) 14,194,024,448 bytes free
0
0
>(by)
0
0
-------------------------------------------------------------------
Quite a weird feeling. I can imagine GCL subprocesses running on an
OpenMosix distributed parallel processing system - another reason to keep
the system small for communication efficiency across slow network
communications systems.
Thanks for the help - lets hope noone finds anything serious over the
weekend despite vast quantities of testing.
Cheers
Mike Thomas
- Re: [Gcl-devel] ANSI Windows: in-package failure, (continued)
- Re: [Gcl-devel] ANSI Windows: in-package failure, Mike Thomas, 2004/02/09
- Re: [Gcl-devel] ANSI Windows: in-package failure, Camm Maguire, 2004/02/11
- RE: [Gcl-devel] ANSI Windows: in-package failure, Mike Thomas, 2004/02/15
- Re: [Gcl-devel] ANSI Windows: in-package failure, Camm Maguire, 2004/02/16
- RE: [Gcl-devel] ANSI Windows: in-package failure, Mike Thomas, 2004/02/16
- Re: [Gcl-devel] ANSI Windows: in-package failure, Camm Maguire, 2004/02/17
- RE: [Gcl-devel] ANSI Windows: in-package failure, Mike Thomas, 2004/02/17
- Re: [Gcl-devel] ANSI Windows: in-package failure, Camm Maguire, 2004/02/18
- RE: [Gcl-devel] ANSI Windows: in-package failure, Mike Thomas, 2004/02/18
- Re: [Gcl-devel] ANSI Windows: in-package failure, Camm Maguire, 2004/02/19
- RE: [Gcl-devel] ANSI Windows: in-package failure,
Mike Thomas <=
- Re: [Gcl-devel] ANSI Windows: in-package failure, Camm Maguire, 2004/02/20
- Re: [Gcl-devel] ANSI Windows: in-package failure, Camm Maguire, 2004/02/11
- RE: [Gcl-devel] ANSI Windows: in-package failure, Mike Thomas, 2004/02/11
Re: [Gcl-devel] Window ansi crash debug output, Camm Maguire, 2004/02/02