Re: Guidance requested for debugging import problem.

[Matt Welland]

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?

On Thu, Nov 11, 2021 at 8:17 PM Matt Welland <mattrwelland@gmail.com> wrote:

Background: I've converted a flat (compilation units but not modules) chicken program to modules and from chicken 4.12 to chicken 5.2. There are two executables, a command-line only and a gui using iup.

The problem: The command-line program runs fine from any directory however the IUP gui program only works from the directory where it was compiled. When run from a different directory I get an error "Error: (import-syntax) during expansion of (import-syntax ...) - cannot import from undefined module
debugprint".

I'm looking for suggestions on how to debug this further.

Thanks.

--

Complexity is your enemy. Any fool can make something complicated.

It is hard to keep things simple. - Richard Branson.

--

--

Complexity is your enemy. Any fool can make something complicated.

It is hard to keep things simple. - Richard Branson.