- Snow-users-list - mailman.iro.umontreal.ca

A few questions... and a suggestion.
by Matthew Martin 23 Fév '08

23 Fév '08

A warning: I'm a noob, to both Scheme and Snow. First question. I have a snowball of pregexp[1] just about ready to upload, and I was wondering what would be appropriate to put as 'license:' ? Its license states: ----- Copyright (c) 1999-2005, Dorai Sitaram. All rights reserved. Permission to copy, modify, distribute, and use this work or a modified copy of this work, for any purpose, is hereby granted, provided that the copy includes this copyright notice, and in the case of a modified copy, also includes a notice of modification. This work is provided as is, with no warranty of any kind. ----- I'm not sure how picky license: is. Would (license: bsd/mit-like) be ok? Something more descriptive? I'll probably email Dorai and ask if they'd prefer to maintain it or sign it as well before I upload the snowball. Probably be good to ask them what a good description of the license as a symbol would be too. OK, next question. How the heck do I use snow from a REPL o_O Let's say I have this in an emacs buffer: ----- (package* test/v1.0.0 (require: time/v1)) (display (current-time-seconds)) ----- I hit C-c C-l to load and eval it, and it says current-time-seconds is undefined? If I instead slap ":";exec snow -- "$0" "$@" on top and run it as a snow script from a command line, it does what I'd expect it to do. Same results with MzScheme and Chicken so far. I cannot for the life of me figure out why it'd work one way and not the other, I assume I'm doing something fundamentally wrong. Last question. For now ;) What exactly are the differences between these?: load-program* include-program* load* include* include*-cd Only include* seems to be documented, as far as I can tell. I suspect one of the -program* variety may resolve the REPL issue above, but I can't quite seem to penetrate the code. And a suggestion: It'd be nice if the docs mentioned that if you're using a *BSD, you probably want to use gtar when creating snowballs. I was racking my brain for a while on that one. Using NetBSD's default tar at least, seems to confuse snowman when it tries to unpack the snowball saying something about invalid filenames. More docs for the various loads and includes would be handy as well. I'd be willing to document them, if I understood them. [1] http://www.ccs.neu.edu/home/dorai/pregexp/pregexp.html

2 3

Re: [Snow-users-list] [gambit-list] AWS, Termite, and Snow
by Marc Feeley 30 Jan '08

30 Jan '08

On 29-Jan-08, at 11:29 PM, Joe Hosteny wrote: > Hi all, > > First of all, let me preface this email with a disclaimer. I'm fairly > new (again) to Scheme (last exposure was 10+ years ago in college). > I'm still feeling my way around a bit, and have settled on Gambit, > Chicken, and PLT, to a lesser extent. What I'm trying to say is - dumb > questions may follow! > > I recently wrote a library to manage a cluster of machines in > Amazon's EC2. I'm looking to totally rewrite it, and port it to Scheme > in the process. I was also looking at having some facility for > managing the cluster from within, with event monitoring via SQS or > Termite. Currently, the library does that via polling from a machine > external to the cluster. It's not ideal, but was sufficient to get my > application working. > > As a start, I wrote a simple Snow package to do MD5 and SHA1 HMAC > calculations (the AWS query string API uses SHA1 signatures). The "digest" Snow package does MD5, SHA1, and other digests: http://snow.iro.umontreal.ca/?viewpkg=digest > I > started to look around for some utilities for URI parsing and encoding > for use in Gambit, but didn't seem to find anything. So, first > question - is anyone aware of a suitable package for this? Check examples/web-server/http.scm in the Gambit distribution. > Second > question - if one doesn't exist, what do people do for regular > expression parsing in Gambit? I normally use pregexp: http://www.ccs.neu.edu/home/dorai/pregexp/pregexp.html . It is well written and portable, so it shouldn't be hard to turn it into a Snow module. > Since I haven't really fleshed out the new architecture, I'm not sure > it's a requirement that I host code to both communicate events across > the cluster and issue AWS API calls from within the same executable. > So I guess an option would be to use Chicken for the HTTP stuff, and > Gambit for Termite and making calls to the code written with Chicken > (though at that point, it may make sense to just use one of the Ruby > or Java libs for that part). I'd prefer not to, if for nothing more > than to be able to contribute the AWS portion as a Chicken or Snow > package. > > So, a few general questions follow. From recent mailing list > discussions, it sounds like Termite will be targeted towards Gambit > only, for the time being at least. Guillaume, is that correct? If not, > do you have an idea of when it might be seen on other Schemes > (specifically, Chicken or PLT)? > > Also, does anyone have a feel for what is going on with Snow? It > seems like the traffic on the mailing list is a bit slow, and the > number of packages is still relatively few. I'm still very much interested in continuing to develop Snow. However I've been busy with other things recently and hope to get back to maintaining Snow more actively soon. To ease the workload I'm also looking for someone to take on some of the maintenance tasks. Is anyone interested in getting involved? Marc

2 1

Install script needs to be updated (Time self-test fails)
by Joe Hosteny 30 Jan '08

30 Jan '08

Hi all, I just tried installing Snow to a new machine, and the time self- tests fail. I think that the current test.scm file checks to make sure the time since epoch is roughly in the period from the beginning of 2007 to the beginning of 2008. --Joe

1 1

Problem installing Snow w/Gambit
by Joe Hosteny 29 Jan '08

29 Jan '08

Hi all, I'm also seeing this. Any ideas? I'm using Gambit v4.1.2. Do I need to be using an older version? --Joe Setting up for SNOW_HOST=gambit compiling aes/v1.0.1 *** ERROR IN "/Users/jhosteny/.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/jhosteny/.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/jhosteny/.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/jhosteny/.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/jhosteny/.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/jhosteny/.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/jhosteny/.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/jhosteny/.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/jhosteny/.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/jhosteny/.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/jhosteny/.snow-site/v1.1.1/pack/genport/v1.0.1/ snow/genport.scm"@20.3 -- Ill-placed 'define' compiling homovector/v1.0.1 *** ERROR IN "/Users/jhosteny/.snow-site/v1.1.1/pack/homovector/v1.0.1/ snow/homovector.scm"@15.3 -- Ill-placed 'define-macro' compiling hostos/v1.0.3 *** ERROR IN "/Users/jhosteny/.snow-site/v1.1.1/pack/hostos/v1.0.3/ snow/hostos.scm"@15.3 -- Ill-placed 'define' compiling http/v1.0.2 compiling list/v1.0.1 *** ERROR IN "/Users/jhosteny/.snow-site/v1.1.1/pack/list/v1.0.1/snow/ list.scm"@14.3 -- Ill-placed 'define' compiling mime/v1.0.1 *** ERROR IN "/Users/jhosteny/.snow-site/v1.1.1/pack/mime/v1.0.1/snow/ mime.scm"@33.3 -- Ill-placed 'define' compiling random/v1.0.1 *** ERROR IN "/Users/jhosteny/.snow-site/v1.1.1/pack/random/v1.0.1/ snow/random.scm"@14.3 -- Ill-placed 'define' compiling rfc1423/v1.0.1 compiling rsa/v1.0.1 *** ERROR IN "/Users/jhosteny/.snow-site/v1.1.1/pack/rsa/v1.0.1/snow/ rsa.scm"@16.3 -- Ill-placed 'define' compiling snowfort-app/v1.0.1 *** ERROR IN "/Users/jhosteny/.snow-site/v1.1.1/pack/snowfort-app/ v1.0.1/snow/snowfort-app.scm"@14.3 -- Ill-placed 'define' compiling snowlib/v1.2.1 *** ERROR IN "/Users/jhosteny/.snow-site/v1.1.1/pack/snowlib/v1.2.1/ snow/snowlib.scm"@14.3 -- Ill-placed 'define' compiling snowman-app/v1.0.2 *** ERROR IN "/Users/jhosteny/.snow-site/v1.1.1/pack/snowman-app/ v1.0.2/snow/snowman-app.scm"@14.3 -- Ill-placed 'define' compiling sort/v1.0.1 *** ERROR IN "/Users/jhosteny/.snow-site/v1.1.1/pack/sort/v1.0.1/snow/ sort.scm"@14.3 -- Ill-placed 'define' compiling string/v1.0.2 *** ERROR IN "/Users/jhosteny/.snow-site/v1.1.1/pack/string/v1.0.2/ snow/string.scm"@14.3 -- Ill-placed 'define' compiling tar/v1.0.1 *** ERROR IN "/Users/jhosteny/.snow-site/v1.1.1/pack/tar/v1.0.1/snow/ tar.scm"@31.3 -- Ill-placed 'define' compiling tcpip/v1.1.2 *** ERROR IN "/Users/jhosteny/.snow-site/v1.1.1/pack/tcpip/v1.1.2/snow/ tcpip.scm"@14.3 -- Ill-placed 'define' compiling time/v1.0.2 *** ERROR IN "/Users/jhosteny/.snow-site/v1.1.1/pack/time/v1.0.2/snow/ time.scm"@14.3 -- Ill-placed 'define' compiling ttyui/v1.0.1 *** ERROR IN "/Users/jhosteny/.snow-site/v1.1.1/pack/ttyui/v1.0.1/snow/ ttyui.scm"@14.3 -- Ill-placed 'define' compiling vector/v1.0.1 *** ERROR IN "/Users/jhosteny/.snow-site/v1.1.1/pack/vector/v1.0.1/ snow/vector.scm"@14.3 -- Ill-placed 'define' compiling zlib/v1.0.1 *** ERROR IN "/Users/jhosteny/.snow-site/v1.1.1/pack/zlib/v1.0.1/snow/ zlib.scm"@22.3 -- Ill-placed 'define' rm -f /Users/jhosteny/.snow-site/current ln -s /Users/jhosteny/.snow-site/v1.1.1 /Users/jhosteny/.snow-site/ current Don't forget to add /Users/jhosteny/.snow-site/current/bin to your PATH

1 0

installation problems
by Derrell Piper 26 Jan '08

26 Jan '08

To answer my own question... The self-test (in test.scm) for the built-in time package is basically a sanity check on the current time (expressed as seconds since Jan 1, 1970, the UNIX system base time): (let* ((range-lo (string->bignum "1168000000")) (range-hi (string->bignum "1200000000")) (s start-time)) (if (not (and (bignum>= s range-lo) (bignum<= s range-hi))) (failed `(and (bignum>= ,s ,range-lo) (bignum<= ,s ,range-hi))))) ...which doesn't seem to play very well with the current time: % date +%s 1201357774 Looks like we're about 15.71 days past snow's expiration date. :-) So I changed mine to "1210000000", which is good for another 3.17 years and I'm off and running. Derrell

1 0

installation problems
by Derrell Piper 26 Jan '08

26 Jan '08

New snow user here... I have MIT/GNU Scheme (7.7.90), Chicken (2.740), and Gambit (v4.1.2 w/ Termite) installed and running fine. I'm trying to install snow-generic-v1.1.1 and attached is what I'm seeing when I do a './configure --site-root=$HOME/.snow-site -- install-hosts=yes' against the latest tarball. So, I guess the 'time' self test is failing across the boards, but I'm also not sure what to make of the 'hostossh: line 1: unknowncommand: command not found' message. A quick grep in the snow directory didn't point me at anything obvious. What am I missing? Thanks! fluffy% uname -a Darwin fluffy.local 8.11.0 Darwin Kernel Version 8.11.0: Wed Oct 10 18:26:00 PDT 2007; root:xnu-792.24.17~1/RELEASE_PPC Power Macintosh powerpc Searching for the Scheme systems accessible in the current PATH: Chicken 2.740 -> /usr/local/bin/csi Chicken compiler 2.740 -> /usr/local/bin/csc Gambit 4.1.2 -> /usr/local/Gambit-C/current/bin/gsi Gambit compiler 4.1.2 -> /usr/local/Gambit-C/current/bin/gsc Gauche 0.8.9 -> /Users/ddp/.snow-site/v1.1.1/bin/gosh MIT Scheme 7.7.90.+ -> /usr/local/bin/mit-scheme MzScheme 360 -> /Users/ddp/.snow-site/v1.1.1/bin/mzscheme Petite Chez Scheme 7.3 -> /Users/ddp/.snow-site/v1.1.1/bin/petite Scheme48 1.4 -> /Users/ddp/.snow-site/v1.1.1/bin/scheme48 Scsh 0.6.7 -> /usr/local/bin/scsh STklos 0.82 -> /Users/ddp/.snow-site/v1.1.1/bin/stklos These systems were not found (you might want to check the URL to install them): bigloo -> http://www-sop.inria.fr/mimosa/fp/Bigloo chez -> http://www.scheme.com guile -> http://www.gnu.org/software/guile kawa -> http://www.gnu.org/software/kawa larceny -> http://www.ccs.neu.edu/home/will/Larceny rscheme -> http://www.rscheme.org scm -> http://www-swiss.ai.mit.edu/~jaffer/SCM.html sisc -> http://sisc.sourceforge.net stalin -> http://en.wikipedia.org/wiki/Stalin_Scheme_compiler Testing the Scheme systems: ----------------------------------------------- testing chicken START OF SELF TEST exceptions, records, optional parameters, keywords, fixnum, homovector, timeFAILED: (and (bignum>= #u16(1 9698 7785 4) #u16(1 1024 5753 4)) (bignum<= #u16(1 9698 7785 4) #u16(1 3072 7706 4))) , bignum, string, filesys, hostossh: line 1: unknowncommand: command not found , random, extio, genport, digest, aes, http, zlib, tar END OF SELF TEST *** 1 TESTS FAILED *** chicken has ***failed*** the self test ----------------------------------------------- testing gambit START OF SELF TEST exceptions, records, optional parameters, keywords, fixnum, homovector, timeFAILED: (and (bignum>= 1201300987 1168000000) (bignum<= 1201300987 1200000000)) , bignum, string, filesys, hostossh: line 1: unknowncommand: command not found , random, extio, genport, digest, aes, http, zlib, tar END OF SELF TEST *** 1 TESTS FAILED *** gambit has ***failed*** the self test ----------------------------------------------- testing gauche START OF SELF TEST exceptions, records, optional parameters, keywords, fixnum, homovector, timeFAILED: (and (bignum>= 1201300990 1168000000) (bignum<= 1201300990 1200000000)) sh: line 1: unknowncommand: command not found , bignum, string, filesys, hostos, random, extio, genport, digest, aes, http, zlib, tar END OF SELF TEST *** 1 TESTS FAILED *** gauche has ***failed*** the self test ----------------------------------------------- testing mit START OF SELF TEST exceptions, records, optional parameters, keywords, fixnum, homovector, timeFAILED: (and (bignum>= 1201301056 1168000000) (bignum<= 1201301056 1200000000)) , bignum, string, filesys, hostostcsh: unknowncommand: Command not found. , random, extio, genport, digest, aes, http, zlib, tar END OF SELF TEST *** 1 TESTS FAILED *** mit has ***failed*** the self test ----------------------------------------------- testing mzscheme START OF SELF TEST exceptions, records, optional parameters, keywords, fixnum, homovector, timeFAILED: (and (bignum>= 1201301082 1168000000) (bignum<= 1201301082 1200000000)) /bin/sh: line 1: unknowncommand: command not found , bignum, string, filesys, hostos, random, extio, genport, digest, aes, http, zlib, tar END OF SELF TEST *** 1 TESTS FAILED *** mzscheme has ***failed*** the self test ----------------------------------------------- testing petite START OF SELF TEST exceptions, records, optional parameters, keywords, fixnum, homovector, timeFAILED: (and (bignum>= 1201301084 1168000000) (bignum<= 1201301084 1200000000)) , bignum, string, filesys, hostossh: line 1: unknowncommand: command not found , random, extio, genport, digest, aes, http, zlib, tar END OF SELF TEST *** 1 TESTS FAILED *** petite has ***failed*** the self test ----------------------------------------------- testing scheme48 Welcome to Scheme 48 1.4 (made by ddp on Fri Jan 25 11:57:04 PST 2008) Copyright (c) 1993-2006 by Richard Kelsey and Jonathan Rees. Please report bugs to scheme-48-bugs(a)s48.org. Get more information at http://www.s48.org/. Type ,? (comma question-mark) for help. > > ; no values returned > ; no values returned > ./base/compat-scheme48.scm ; no values returned > ./base/snow.scm #f > ./pack/snowlib/v1.2.1/snow/snowlib.scm ./pack/tcpip/v1.1.2/snow/tcpip.scm ./pack/extio/v1.0.3/snow/extio.scm ./pack/time/v1.0.2/snow/time.scm ./pack/string/v1.0.2/snow/string.scm ./pack/fixnum/v1.0.3/snow/fixnum.scm ./pack/homovector/v1.0.1/snow/homovector.scm ./pack/mime/v1.0.1/snow/mime.scm ./pack/aes/v1.0.1/snow/aes.scm ./pack/binio/v1.0.2/snow/binio.scm ./pack/base64/v1.0.1/snow/base64.scm ./pack/digest/v1.0.1/snow/digest.scm ./pack/bignum/v1.0.1/snow/bignum.scm ./pack/random/v1.0.1/snow/random.scm ./pack/filesys/v1.0.4/snow/filesys.scm ./pack/genport/v1.0.1/snow/genport.scm ./pack/tar/v1.0.1/snow/tar.scm ./pack/zlib/v1.0.1/snow/zlib.scm ./pack/hostos/v1.0.3/snow/hostos.scm ./pack/http/v1.0.2/snow/http.scm ./test.scm START OF SELF TEST exceptions, records, optional parameters, keywords, fixnum, homovector, timeFAILED: (and (bignum>= 1201301099 1168000000) (bignum<= 1201301099 1200000000)) , bignum, string, filesyssh: line 1: unknowncommand: command not found , hostos, random, extio, genport, digest, aes, http, zlib, tar END OF SELF TEST *** 1 TESTS FAILED *** scheme48 has ***failed*** the self test ----------------------------------------------- testing scsh START OF SELF TEST exceptions, records, optional parameters, keywords, fixnum, homovector, timeFAILED: (and (bignum>= 1201301117 1168000000) (bignum<= 1201301117 1200000000)) , bignum, string, filesys, hostossh: line 1: unknowncommand: command not found , random, extio, genport, digest, aes, httpChannel closed: 3 3 Channel closed: 4 4 , zlib, tar END OF SELF TEST *** 1 TESTS FAILED *** scsh has ***failed*** the self test ----------------------------------------------- testing stklos START OF SELF TEST exceptions, records, optional parameters, keywords, fixnum, homovector, timeFAILED: (and (bignum>= 1201301125 1168000000) (bignum<= 1201301125 1200000000)) , bignum, string, filesys, hostossh: line 1: unknowncommand: command not found , random, extio, genport, digest, aes, http, zlib, tar END OF SELF TEST *** 1 TESTS FAILED *** stklos has ***failed*** the self test ----------------------------------------------- *** None of the installed Scheme systems support Scheme Now! *** Consequently, the Scheme Now! framework can't be installed. *** You might want to install a Scheme system, add it to your *** PATH, and then run the configure script again.

1 0

AWS
by Joe Hosteny 18 Jan '08

18 Jan '08

Hi everyone, I'm fairly new to Scheme, so I was wondering if someone would like to collaborate with me on (or at least review code for) a Snow package for managing EC2 instances in AWS? I have done a fair amount with EC2 and S3, including writing a system for managing a cluster of EC2 instances (with launch dependencies and cluster-wide event propagation and triggers). I'm considering using Termite as well for a more advanced distributed management infrastructure than what I did before. Cheers, --Joe

1 0

Package model suggestion
by Nikita Sidorov 23 Déc '07

23 Déc '07

Hi all, Scheme is a language of my choice and for me, as probably for many other scheme users, sharing code between different scheme systems is a concern. It is really important to have a platform like Snow where users of all major implementations could effectively collaborate. But it seems to me that Snow has unnecessary limitation of reliyng on portable code only (please, correct me if I'm wrong). It means that a package cannot use a functionality that is not available as a snow package even when the functionality is implemented by most of scheme systems. SRFI-69 (hashtables) is a good example. I think the problem is in the package model. In the current model a package provides only one feature that is the name of the package itself. It also implies that a certain functionality may have only one implementation - a portable one. I'd like to suggest a bit different package model that is alike those used in package managers of linux distributions (rpm,deb). In this model a package may provide several features and several implementations of the same api are possible. In addition, every snow system will have a preinstalled package that provides an implementation-specific feature. For mzscheme it will look something like this: (package* snow-mzscheme (provides mzscheme)) For sisc: (package* snow-sisc (provides sisc)) Having such model we can use implementations of apis specific to scheme system. Let's consider an example with srfi-69. In mzscheme srfi-69 is loaded by this: (require (lib "69.ss" "srfi")) In SISC it is done in this way: (require-library 'sisc/libs/srfi/srfi-69) (import srfi-69) Respective implementation-specific packages will look like this: srfi-69-mzscheme.scm : (package* srfi-69-mzscheme (provides srfi-69) (requires mzscheme)) (require (lib "69.ss" "srfi")) srfi-69-sisc.scm : (package* srfi-69-sisc (provides srfi-69) (requires sisc)) (require-library 'sisc/libs/srfi/srfi-69) (import srfi-69) Similar packages are created for other systems that support srfi-69. Having this done we can create a package that uses srfi-69 and runs on all the platforms that provide it: (package* my-package (requires srfi-69)) (define table (make-hash-table)) ... What do you think about this model? Nikita

2 2

Transitivity of "require" for macros
by François Magnan 22 Déc '07

22 Déc '07

Hi, I suspect a bug in snow (maybe I am wrong) but let's say I have 3 snowballs (dummies for my explanation): ===== moda.scm ====== (package* moda/v1.0.0 (provide: (define (square x)) (define-macro (add x y) `(+ ,x ,y)))) (define (square x) (* x x)) ===== modb.scm ====== (package* modb/v1.0.0 (provide: (define (power4 x))) (require: moda/v1)) (define (power4 x) (* (square x) (square x))) (write (add 1 2)) (newline) ===== modc.scm ====== (package* modc/v1.0.0 (provide: (define (power6 x))) (require: modb/v1)) (define (power6 x) (* (square x) (square x) (square x))) (write (power6 12)) (newline) (write (add 1 2)) (newline) ========================================== Then I type: snow -- modb/v1.0.0/snow/modb.scm 3 which is what I expected. And then I type: snow -- modc/v1.0.0/snow/modc.scm 3 2985984 *** ERROR IN "modc/v1.0.0/snow/modc.scm"@10.9 -- Unbound variable: moda/v1#add which is NOT what I expected. It seems that macros are not transitively transported through dependencies. Normal functions are. Is this a bug? Thank you, Francois Magnan

1 1

srfi1, gambit, mac osx
by Siegfried Gonzi 17 Déc '07

17 Déc '07

hello: i would like to install srfi-1 on gambit-c. i installed snow (also set path in .bashrc), but whenever i do the following i get an error message: snowman install srfi1 == *** WARNING -- Variable "_" used in module "extio.o1" is undefined *** WARNING -- Variable "define*" used in module "extio.o1" is undefined *** WARNING -- Variable "extio/v1.0.3" used in module "extio.o1" is undefined *** WARNING -- Variable "i/o" used in module "extio.o1" is undefined *** WARNING -- Variable "lgpl/v2.1" used in module "extio.o1" is undefined *** WARNING -- Variable "obj" used in module "extio.o1" is undefined *** WARNING -- Variable "package*" used in module "extio.o1" is undefined *** WARNING -- Variable "port" used in module "extio.o1" is undefined *** WARNING -- Variable "snow" used in module "extio.o1" is undefined *** WARNING -- Variable "snow-force-output" used in module "extio.o1" is undefined *** WARNING -- Variable "snow-pretty-print" used in module "extio.o1" is undefined *** ERROR IN | extio.o1| -- Operator is not a PROCEDURE (#!unbound #!unbound) == Is it possible to install srfi-1 by other methods on gambit-c and Mac OSX Leopard? Btw: if anyone here to have Bigloo installed on Mac OSX Leopard please let me know i am in dire need of Bigloo but it does not compile on Leopard. For the moment I am using Gambit-C Thanks, Siegfried Gonzi -- GMX FreeMail: 1 GB Postfach, 5 E-Mail-Adressen, 10 Free SMS. Alle Infos und kostenlose Anmeldung: http://www.gmx.net/de/go/freemail

1 0