> Update. I found that removing the *.import.scm files causes the problem to > also occur when running the executable in the directory where compiled. > However the non-gui executable still works fine. Why would a compiled > Chicken program be reading the import.scm files at run time?
This can depend on compiler options: the import files contain code to register modules and imports, depending on compilation type (static/dynamic) and certain compiler options, this code is compiled into the executable or is loaded from a separate file. If you run the binaries with "-:d" and/or "-:d" do you get any information regarding the loaded files? felix
