|Subject:||[Chicken-users] Module unresolved error|
|Date:||Tue, 14 Jun 2016 11:09:09 -0400|
I’m new to CHICKEN and I’m working on converting a large Guile codebase to CHICKEN. The codebase is a collection of shared libraries (each library in a separate .scm file), collectively known as “lab-core”. So, I’ve packaged it all as an egg called “lab-core” with each individual .scm file as it’s own module (under different names). Does this seem like a reasonable way to package such a project?
As I go file by file converting to CHICKEN modules, I keep running into “module unresolved” errors when attempting to install my egg via chicken-install.
Unfortunately, the output gives no indication of which function is causing the error or why, and the only way I’ve been able to figure this out is by commenting out chunks of code and narrowing down until I find the offending function. If I delete that function, the module compiles perfectly and I can use the rest of the functions just as you would expect. What does "module unresolved” mean and is there a better way to figure out what is causing it?
I’ve attached a MWE where loglevel is a stripped-down version of one such library causing the “module unresolved” error. Here are the steps to reproduce:
$ cd lab-core
lab-core$ chicken-install -debug
(see attached output.txt for the debug output)
Compare this to:
> (load “loglevel-no-module.scm”)
> (err-puts "foo" 42 "!”)
which shows my functions working perfectly as long as I’m not using module syntax.
Why would compiling into a module cause an error when my functions work fine in the REPL? Any help would be appreciated.
Chicken Version 22.214.171.124 (stability/4.8.0) (rev 5bd53ac)
linux-unix-gnu-x86-64 [ 64bit manyargs dload ptables ]
compiled 2013-10-03 on aeryn.xorinia.dim (Darwin)
installed via sudo apt-get install chicken-bin
Description: Zip archive
Description: Binary data
Description: Text document
Description: S/MIME cryptographic signature
|[Prev in Thread]||Current Thread||[Next in Thread]|