[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Gcl-devel] Re: Axiom/GCL on Windows
From: |
Camm Maguire |
Subject: |
[Gcl-devel] Re: Axiom/GCL on Windows |
Date: |
05 Dec 2006 20:51:29 -0500 |
User-agent: |
Gnus/5.09 (Gnus v5.9.0) Emacs/21.2 |
Greetings!
Gabriel Dos Reis <address@hidden> writes:
> On Tue, 5 Dec 2006, Camm Maguire wrote:
>
> | > I tried the following, and got the same result
> | >
> | > ./gcl
> | > >(compiler::link nil "foo")
> | >
> | >
> |
> | Yes, please do
> |
> | >(defun delete-file (&rest r) nil)
> | >(trace system)
> | >(compiler::link nil "foo")
> |
> | and see where the error comes up.
>
> The first call to system to compiler ./user-init.c was OK.
> The second call to system to link and produce an excutable
> ./raw_foo.exe was OK too.
>
> The error happens on the third call to system to execute ./raw_foo.exe.
>
> The exact command that trace shows is:
>
> (SYSTEM "./raw_foo.exe
> C:/msys/1.0/home/gdr/build/axiom/build/i686-pc-mingw32/lib/gcl-2.6.8/unixport/
> < init_foo.lsp")
>
> trace shows system exited as
> (SYSTEM 0 1)
>
> | If you are left with the raw image, in the shell you can try
> |
> | ./raw_foo ./ <init_foo.lsp
>
> That prompted an MS bugreport widget saying that raw_foo.exe has
> encountered a problem and needs to close. :-/
>
What a delightfully descriptive message! Next step is to build with
--enable-debug at the configure command line and run raw_foo as above
under gdb. might want to break at abort, exit, main and malloc.
> Do you need me to send the content of init_foo.lsp, or is pretty
> standard stuff?
>
Don't think this is necessary.
Take care,
> Thanks,
>
> -- Gaby
>
>
>
--
Camm Maguire address@hidden
==========================================================================
"The earth is but one country, and mankind its citizens." -- Baha'u'llah