Greetins! Gabriel Dos Reis <[EMAIL PROTECTED]> writes:
> On Tue, 5 Dec 2006, Camm Maguire wrote: > > | > The error I'm having is that the linker complains it can't find the > | > symbols which are supposed to be in the winsock dll. The error > | > message includes > | > > | > undefined reference to [EMAIL PROTECTED]' > | > undefined reference to [EMAIL PROTECTED]' > | > undefined refenrece to [EMAIL PROTECTED]' > | > > | > | OK, for this, just add -lwinsock after libspad.a on the compiler::link > | command line. In general, you can link any shared lib in this way. > > Hi Camm, that helped. > > That is all the symbols seem to be satisfied now. However, no image is > produced; rather I got a diagnostic message which I don't quite > understand (except that it surely has to do with Windows shell) > > '.' is not recognized as an internal or external command. > operable program or batch file. > > > and no produced executab;e image. The system procudes the > raw_lisp_map, but nothing else. > > 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. If you are left with the raw image, in the shell you can try ./raw_foo ./ <init_foo.lsp Take care, > Note that if I do > > ./gcl > >(si::save-system "bar") > > I indeed have a working bar.exe image. > > Suggestions? > > Thanks, > > -- Gaby > > > -- Camm Maguire [EMAIL PROTECTED] ========================================================================== "The earth is but one country, and mankind its citizens." -- Baha'u'llah _______________________________________________ Gcl-devel mailing list Gcl-devel@gnu.org http://lists.gnu.org/mailman/listinfo/gcl-devel
