search

marcomaggi / vicare

A native compiler for Scheme compliant with R6RS
http://marcomaggi.github.com/vicare.html
Other
200 stars 34 forks source link

Can't (import (vicare)) #28

Closed ghost closed 13 years ago

ghost commented 13 years ago

Hello! If I understood the documentation correctly, (import (vicare)) should have the same effect as (import (ikarus)).

From the documentation:

3 Extensions library

In addition to the libraries listed in the R6RS standard, Vicare offers the (ikarus) and (vicare) libraries which provide additional features; (ikarus) is a composite library, it exports a superset of all the supported bindings of R6RS; (vicare) exports the same bindings of (ikarus).

Now, in my machine, they are not the same. I can (import (ikarus)), but cannot (import (vicare)).

darkam andres /home/andres/scheme $ vicare
*** vicare warning: optimization level artificially set to 0.
Vicare Scheme version 0.1b1+ (revision 3e33f3b1ff6f1f076491569949a5e0ba2e7663c6, build 2011-10-26)
Copyright (c) 2006-2010 Abdulaziz Ghuloum and contributors

> (library-path)
("/usr/lib" "/home/andres/scheme/vicare/lib/vicare")
> (import (ikarus))
> (import (vicare))
Unhandled exception
 Condition components:
   1. &error
   2. &who: expander
   3. &message: "cannot locate library in library-path"
   4. &library-resolution:
       library: (vicare)
       files: ("/usr/lib/vicare/main.vicare.sls" "/usr/lib/vicare/main.vicare.ss" "/usr/lib/vicare/main.vicare.scm" "/usr/lib/vicare/main.sls" "/usr/lib/vicare/main.ss" "/usr/lib/vicare/main.scm" "/usr/lib/vicare.vicare.sls" "/usr/lib/vicare.vicare.ss" "/usr/lib/vicare.vicare.scm" "/usr/lib/vicare.sls" "/usr/lib/vicare.ss" "/usr/lib/vicare.scm" "/home/andres/scheme/vicare/lib/vicare/vicare/main.vicare.sls" "/home/andres/scheme/vicare/lib/vicare/vicare/main.vicare.ss" "/home/andres/scheme/vicare/lib/vicare/vicare/main.vicare.scm" "/home/andres/scheme/vicare/lib/vicare/vicare/main.sls" "/home/andres/scheme/vicare/lib/vicare/vicare/main.ss" "/home/andres/scheme/vicare/lib/vicare/vicare/main.scm" "/home/andres/scheme/vicare/lib/vicare/vicare.vicare.sls" "/home/andres/scheme/vicare/lib/vicare/vicare.vicare.ss" "/home/andres/scheme/vicare/lib/vicare/vicare.vicare.scm" "/home/andres/scheme/vicare/lib/vicare/vicare.sls" "/home/andres/scheme/vicare/lib/vicare/vicare.ss" "/home/andres/scheme/vicare/lib/vicare/vicare.scm")
>

Is this expected behaviour, or a bug? Am I missing something?

Thanks,

Andrés.

marcomaggi commented 13 years ago

"Andrés Musetti" wrote:

If I understood the documentation correctly, (import (vicare)) should have the same effect as (import (ikarus)).

Yes:

$ vicare Vicare Scheme version 0.2d1 Revision devel/d9c395b8397136730cf718c48e0780b9a7183400 Build 2011-10-28

Copyright (c) 2006-2010 Abdulaziz Ghuloum and contributors Copyright (c) 2011 Marco Maggi

vicare> (import (vicare)) vicare> (import (ikarus)) vicare> (import (rnrs)) vicare>

It seems to me that you have an old revision; if you have git installed, can you try with a checkout of "devel" branch from GitHub? Else, I have uploaded a tarball with the current "devel" HEAD revision:

https://github.com/downloads/marcomaggi/vicare/vicare-0.2d1-1.tar.gz

Sorry for this problem; it is probably a confusion caused by the fact that I am trying to switch from uploading tarballs to GitHub's download area, to relying on GitHub's feature of allowing checkout of tagged revisions from a separate page. But I realise now that there are problems, because some of the files needed to build are not available in those tagged tarballs.

HTH