Ian, what does "csi -v" show? Perhaps dynamic loading isn't
available (this is controlled by some preprocessor macros).
The srfi's are put into libchicken, extensions exist as separate
dll's (that results in different semantics and error-messages).
Does windows accept executable names in double-quotes?
If it does, I can try to address the space-in-pathname issue
in csc.scm(.in).
I've attached some output below. "csi -v" mentions dload at least. And
windows looks like it does accept executable names in double-quotes, or it
does from the windows shell at least.
C:\Program Files\Chicken\bin>set PATH=C:\Program Files\Chicken\bin;%PATH%
C:\Program Files\Chicken\bin>csi -v
___| | _) |
| __ \ | __| | / _ \ __ \
| | | | | ( < __/ | |
\____|_| |_|_|\___|_|\_\\___|_| _|
Version 2, Build 325 - windows-mingw32-x86 - [ dload ptables applyhook ]
(c)2000-2006 Felix L. Winkelmann
C:\Program Files\Chicken\bin>"c:\Program Files\Chicken\bin\csi"
___| | _) |
| __ \ | __| | / _ \ __ \
| | | | | ( < __/ | |
\____|_| |_|_|\___|_|\_\\___|_| _|
Version 2, Build 325 - windows-mingw32-x86 - [ dload ptables applyhook ]
(c)2000-2006 Felix L. Winkelmann
#;1> (exit)
Ian
_______________________________________________
Chicken-users mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/chicken-users
