Snow-users-list] Difficulties on Gambit
On Wed, Mar 12, 2008 at 9:26 AM, Joel J. Adamson <jadamson@partners.org> wrote:
"Matthew Martin" <matt.a.martin@gmail.com> writes:
On Tue, Mar 11, 2008 at 2:56 PM, Joel J. Adamson <jadamson@partners.org> wrote:
That's an old problem... kinda surprised it's still there.
I know there was discussion of it on the list (I checked the archives). This was in a download of snow-generic from the main download page. Is there a VC repository somewhere?
I'm not sure.
2 things.
1) It's "srfi1", not "srfi-1". However, it should simply reply with "Snowfort does not contain package srfi-1." -------------------------------------------- Martin@Deimos $ snowman install srfi-1 Snowfort does not contain package srfi-1. --------------------------------------------- (the above is using mzscheme)
Yeah, I get exactly the same message when I try any snowman command. I just tried it with those environment variables, and I get the same thing.
2) I get the same error you did when I try 'env SNOW_HOST=gambit snowman install srfi-1' or 'env SNOW_HOST=gambit snowman install srfi1'. gsi is also in my $PATH.
It would seem the immediate solution is to try a different Scheme implementation for the time being until someone more knowledgeable responds.
I'd love to take your suggestion, but I'm hooked on Gambit ;)
Here's what happens if I try guile: ,---- | | /home/joel/lisp/scm/.snow: Zshell> SNOW_HOST=guile snowman install srfi1 | ERROR: In procedure scm_lreadr: | ERROR: #<unknown port>:5:220: illegal character in escape sequence: #\3 `----
Same here on Guile 1.8.3 : ----------------------------------------------------------------- Deimos $ SNOW_HOST=guile snowman install srfi1 ERROR: In procedure scm_lreadr: ERROR: #<unknown port>:5:220: illegal character in escape sequence: #\3 ------------------------------------------------------------------ And on Chicken v. 2.608 - netbsd-unix-gnu-x86 I get: ------------------------------------------------------------------- Martin@Deimos $ SNOW_HOST=chicken snowman install srfi1 Warning: undefined escape sequence in string - probably forgot backslash ? in line 5 #\3 Warning: undefined escape sequence in string - probably forgot backslash ? in line 21 #\3 Warning: undefined escape sequence in string - probably forgot backslash ? in line 21 #\2 Warning: undefined escape sequence in string - probably forgot backslash ? in line 21 #\3 Warning: undefined escape sequence in string - probably forgot backslash ? in line 21 #\2 Warning: undefined escape sequence in string - probably forgot backslash ? in line 21 #\3 Warning: undefined escape sequence in string - probably forgot backslash ? in line 21 #\2 Warning: undefined escape sequence in string - probably forgot backslash ? in line 21 #\3 Warning: undefined escape sequence in string - probably forgot backslash ? in line 21 #\2 Warning: undefined escape sequence in string - probably forgot backslash ? in line 39 #\3 Warning: undefined escape sequence in string - probably forgot backslash ? in line 39 #\2 srfi1/v1.0.16/snow/srfi-1-reference.scm -- invalid signature by: ("Jeremie Lasalle Ratelle <pouexmachinax at gmail.com>") srfi1/v1.0.16/snow/srfi-1-tests.scm -- invalid signature by: ("Jeremie Lasalle Ratelle <pouexmachinax at gmail.com>") srfi1/v1.0.16/snow/srfi1.scm -- invalid signature by: ("Jeremie Lasalle Ratelle <pouexmachinax at gmail.com>") Package srfi1/v1.0.16 failed verification. The verification may succeed if one of the following certificates is imported: 1) "Jeremie Lasalle Ratelle <pouexmachinax at gmail.com>" fingerprint: c113604551030ec83b040dd737fad9bb purpose: (snow) authenticity: *** not signed *** ASCII: 2VydC12MQoiSmVyZW1pZSBMYXNhbGxlIFJhdGVsbGUgPHBvdWV4bWFjaGluYXggYXQgZ21haWwuY29tPiIKKCJSMkFEUXc9PSIgIlNVRTJ3dz09IikKKHNub3cpCig1MTIgIkFjTmtENk5uRzNjMHNNODRONUZYMWRxakJ0T1owWVZlNFd5TUZTTXdBbWVsM0dhNXlTNFB4cnBOYjVXLzBVcERxc0ZVTlhjdFpXdUgzeWFjdG5ESUYrYz0iICJBUUFCIikKI2YK Deimos $ ------------------------------------------------------------------------------ (the invalid signature stuff is OK, I just havn't imported his key).
Afficher les réponses par date
Okay I reinstalled gambit v4.2.3 with latest patches and I reinstalled the latest snow and ... jeremie$ snowman *** WARNING -- Variable "_" used in module "extio.o2" is undefined *** WARNING -- Variable "define*" used in module "extio.o2" is undefined *** WARNING -- Variable "extio/v1.0.3" used in module "extio.o2" is undefined *** WARNING -- Variable "i/o" used in module "extio.o2" is undefined *** WARNING -- Variable "lgpl/v2.1" used in module "extio.o2" is undefined *** WARNING -- Variable "obj" used in module "extio.o2" is undefined *** WARNING -- Variable "package*" used in module "extio.o2" is undefined *** WARNING -- Variable "port" used in module "extio.o2" is undefined *** WARNING -- Variable "snow" used in module "extio.o2" is undefined *** WARNING -- Variable "snow-force-output" used in module "extio.o2" is undefined *** WARNING -- Variable "snow-pretty-print" used in module "extio.o2" is undefined *** ERROR IN | extio.o2| -- Operator is not a PROCEDURE (#!unbound #!unbound)
"Jeremie Lasalle Ratelle" <pouexmachinax@gmail.com> writes:
Okay I reinstalled gambit v4.2.3 with latest patches and I reinstalled the latest snow and ...
Yeah, I also updated Gambit to 4.2.3, and then updated with hg. I still get the same thing. Joel -- Joel J. Adamson Biostatistician Pediatric Psychopharmacology Research Unit Massachusetts General Hospital Boston, MA 02114 (617) 643-1432 (303) 880-3109 The information transmitted in this electronic communication is intended only for the person or entity to whom it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you received this information in error, please contact the Compliance HelpLine at 800-856-1983 and properly dispose of this information.
On Wed, Mar 12, 2008 at 12:14 PM, Joel J. Adamson <jadamson@partners.org> wrote:
"Jeremie Lasalle Ratelle" <pouexmachinax@gmail.com> writes:
Okay I reinstalled gambit v4.2.3 with latest patches and I reinstalled the latest snow and ...
Yeah, I also updated Gambit to 4.2.3, and then updated with hg. I still get the same thing.
Joel
4.2.0 here.
Okay so the problem was clearly in extio. I tried requiring that in a test package and invoked it with snow -- test.scm and had the same error. And I reinstalled snow with only gambit to see if there were any warnings or errors and compiling aes/v1.0.1 *** ERROR IN "/Users/jeremie/.snow-site/v1.1.1/pack/aes/v1.0.1/snow/aes.scm"@15.3 -- Ill-placed 'define' compiling base64/v1.0.1 *** ERROR IN "/Users/jeremie/.snow-site/v1.1.1/pack/base64/v1.0.1/snow/base64.scm"@14.3-- Ill-placed 'define' compiling bignum/v1.0.1 *** ERROR IN "/Users/jeremie/.snow-site/v1.1.1/pack/bignum/v1.0.1/snow/bignum.scm"@15.3-- Ill-placed 'define' compiling binio/v1.0.2 *** ERROR IN "/Users/jeremie/.snow-site/v1.1.1/pack/binio/v1.0.2/snow/binio.scm"@14.3 -- Ill-placed 'define' compiling cert/v1.0.2 *** ERROR IN "/Users/jeremie/.snow-site/v1.1.1/pack/cert/v1.0.2/snow/cert.scm"@15.3 -- Ill-placed 'define' compiling cgi/v1.0.1 *** ERROR IN "/Users/jeremie/.snow-site/v1.1.1/pack/cgi/v1.0.1/snow/cgi.scm"@14.3 -- Ill-placed 'define' compiling cryptio/v1.0.1 *** ERROR IN "/Users/jeremie/.snow-site/v1.1.1/pack/cryptio/v1.0.1/snow/cryptio.scm"@16.3-- Ill-placed 'define' compiling digest/v1.0.1 *** ERROR IN "/Users/jeremie/.snow-site/v1.1.1/pack/digest/v1.0.1/snow/digest.scm"@14.3-- Ill-placed 'define' compiling extio/v1.0.3 compiling filesys/v1.0.4 *** ERROR IN "/Users/jeremie/.snow-site/v1.1.1/pack/filesys/v1.0.4/snow/filesys.scm"@14.3-- Ill-placed 'define' compiling fixnum/v1.0.3 *** ERROR IN "/Users/jeremie/.snow-site/v1.1.1/pack/fixnum/v1.0.3/snow/fixnum.scm"@14.3-- Ill-placed 'define-macro' compiling genport/v1.0.1 *** ERROR IN "/Users/jeremie/.snow-site/v1.1.1/pack/genport/v1.0.1/snow/genport.scm"@20.3-- Ill-placed 'define' compiling homovector/v1.0.1 ... etc As you can see, extio compiles correctly because there are no define or define-macro in the package* header. I'll see Marc with this problem.
And by the way, if you remove extio.o1 you'll have other warnings concerning rfc1423.o1 and http.o1 Remove those too and you can run snowman. So this is a compilation bug. On Wed, Mar 12, 2008 at 2:12 PM, Jeremie Lasalle Ratelle < pouexmachinax@gmail.com> wrote:
Okay so the problem was clearly in extio. I tried requiring that in a test package and invoked it with snow -- test.scm and had the same error.
And I reinstalled snow with only gambit to see if there were any warnings or errors and
compiling aes/v1.0.1 *** ERROR IN "/Users/jeremie/.snow-site/v1.1.1/pack/aes/v1.0.1/snow/aes.scm"@15.3 -- Ill-placed 'define' compiling base64/v1.0.1 *** ERROR IN "/Users/jeremie/.snow-site/v1.1.1/pack/base64/v1.0.1/snow/base64.scm"@14.3-- Ill-placed 'define' compiling bignum/v1.0.1 *** ERROR IN "/Users/jeremie/.snow-site/v1.1.1/pack/bignum/v1.0.1/snow/bignum.scm"@15.3-- Ill-placed 'define' compiling binio/v1.0.2 *** ERROR IN "/Users/jeremie/.snow-site/v1.1.1/pack/binio/v1.0.2/snow/binio.scm"@14.3-- Ill-placed 'define' compiling cert/v1.0.2 *** ERROR IN "/Users/jeremie/.snow-site/v1.1.1/pack/cert/v1.0.2/snow/cert.scm"@15.3 -- Ill-placed 'define' compiling cgi/v1.0.1 *** ERROR IN "/Users/jeremie/.snow-site/v1.1.1/pack/cgi/v1.0.1/snow/cgi.scm"@14.3 -- Ill-placed 'define' compiling cryptio/v1.0.1 *** ERROR IN "/Users/jeremie/.snow-site/v1.1.1/pack/cryptio/v1.0.1/snow/cryptio.scm"@ 16.3 -- Ill-placed 'define' compiling digest/v1.0.1 *** ERROR IN "/Users/jeremie/.snow-site/v1.1.1/pack/digest/v1.0.1/snow/digest.scm"@14.3-- Ill-placed 'define' compiling extio/v1.0.3 compiling filesys/v1.0.4 *** ERROR IN "/Users/jeremie/.snow-site/v1.1.1/pack/filesys/v1.0.4/snow/filesys.scm"@ 14.3 -- Ill-placed 'define' compiling fixnum/v1.0.3 *** ERROR IN "/Users/jeremie/.snow-site/v1.1.1/pack/fixnum/v1.0.3/snow/fixnum.scm"@14.3-- Ill-placed 'define-macro' compiling genport/v1.0.1 *** ERROR IN "/Users/jeremie/.snow-site/v1.1.1/pack/genport/v1.0.1/snow/genport.scm"@ 20.3 -- Ill-placed 'define' compiling homovector/v1.0.1 ... etc
As you can see, extio compiles correctly because there are no define or define-macro in the package* header. I'll see Marc with this problem.
"Jeremie Lasalle Ratelle" <pouexmachinax@gmail.com> writes:
And by the way, if you remove extio.o1 you'll have other warnings concerning rfc1423.o1 and http.o1
Remove those too and you can run snowman.
I did, and it appears to work: what problems can I expect from deleting those files? Will snowman use the source (.scm) versions? Joel -- Joel J. Adamson Biostatistician Pediatric Psychopharmacology Research Unit Massachusetts General Hospital Boston, MA 02114 (617) 643-1432 (303) 880-3109 The information transmitted in this electronic communication is intended only for the person or entity to whom it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you received this information in error, please contact the Compliance HelpLine at 800-856-1983 and properly dispose of this information.
It will use the source files instead and it will be slower. This is a temporary solution until we find what the problem is. On Wed, Mar 12, 2008 at 2:47 PM, Joel J. Adamson <jadamson@partners.org> wrote:
"Jeremie Lasalle Ratelle" <pouexmachinax@gmail.com> writes:
And by the way, if you remove extio.o1 you'll have other warnings concerning rfc1423.o1 and http.o1
Remove those too and you can run snowman.
I did, and it appears to work: what problems can I expect from deleting those files? Will snowman use the source (.scm) versions?
Joel
-- Joel J. Adamson Biostatistician Pediatric Psychopharmacology Research Unit Massachusetts General Hospital Boston, MA 02114 (617) 643-1432 (303) 880-3109
The information transmitted in this electronic communication is intended only for the person or entity to whom it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you received this information in error, please contact the Compliance HelpLine at 800-856-1983 and properly dispose of this information.
On 12-Mar-08, at 2:49 PM, Jeremie Lasalle Ratelle wrote:
It will use the source files instead and it will be slower.
This is a temporary solution until we find what the problem is.
I found the problem. It is a bug in gsi/main.scm which prevents the - prelude option to gsc to work properly. The -prelude option is used to include the Snow macro definitions (for package*, define*, etc) at the top of the Snow package being compiled. I'll have a fix later tonight. Marc
participants (4)
-
jadamson＠partners.org -
Jeremie Lasalle Ratelle -
Marc Feeley -
Matthew Martin