Re: Guidance requested for debugging import problem.

2021-11-29 Thread Matt Welland
On Mon, 2021-11-29 at 21:16 +0100, felix.winkelm...@bevuta.com wrote: > > Hi! > > The problem here is that read-syntax extensions are not seen by csm, > which > tries to load and parse all source files. This was a blatant > oversight on my part, > I just committed a few changes to the csm trunk th

Re: Guidance requested for debugging import problem.

2021-11-29 Thread felix . winkelmann
> Hi Felix, > > I did not know about csm (or perhaps forgot it's existence?). Anyhow it > seems like a potentially much better solution than a > hand-maintained Makefile. I've tried it on a couple code bases and I'm > running into a few issues, some are just cruft in the code but two cases > I'm ru

Re: Guidance requested for debugging import problem.

2021-11-29 Thread Matt Welland
Hi Felix, I did not know about csm (or perhaps forgot it's existence?). Anyhow it seems like a potentially much better solution than a hand-maintained Makefile. I've tried it on a couple code bases and I'm running into a few issues, some are just cruft in the code but two cases I'm running into in

Re: Guidance requested for debugging import problem.

2021-11-15 Thread felix . winkelmann
> Wow, that seems to have fixed it. Thanks!! Also, I will not tire to point out that "csm" is always a viable alternative! :-) felix

Re: Guidance requested for debugging import problem.

2021-11-14 Thread Matt Welland
Wow, that seems to have fixed it. Thanks!! On Sun, Nov 14, 2021 at 3:54 PM wrote: > > I went ahead and completed the minimal example build including the use of > > .import.o files to enable using modules in evals. See attached tar. It > > works fine which implies that, as you suggested, I have s

Re: Guidance requested for debugging import problem.

2021-11-14 Thread felix . winkelmann
> I went ahead and completed the minimal example build including the use of > .import.o files to enable using modules in evals. See attached tar. It > works fine which implies that, as you suggested, I have something wrong in > my build system. Thanks for the example code, this is really helpful u

Re: Guidance requested for debugging import problem.

2021-11-14 Thread Matt Welland
I went ahead and completed the minimal example build including the use of .import.o files to enable using modules in evals. See attached tar. It works fine which implies that, as you suggested, I have something wrong in my build system. I do think this little sample build might be helpful for othe

Re: Guidance requested for debugging import problem.

2021-11-13 Thread Matt Welland
The .import.o files are there to support access to modules in evals (there is a past email thread on this). Those files are compiled like this: csc -unit apimod.import -c apimod.import.scm -o apimod.import.o I've attached a basic testcase that models the build without the import.o stuff. Please

Re: Guidance requested for debugging import problem.

2021-11-13 Thread felix . winkelmann
> Thanks Felix for looking. Both run with -:d and attached. > > I only see the following loading calls in dashboard.log: > > ; loading /home/matt/data/buildall/ck5.2/lib/chicken/11/ > chicken.time.import.so ... > [debug] loading compiled library > /home/matt/data/buildall/ck5.2/lib/chicken/11/chick

Re: Guidance requested for debugging import problem.

2021-11-12 Thread Matt Welland
Thanks Felix for looking. Both run with -:d and attached. I only see the following loading calls in dashboard.log: ; loading /home/matt/data/buildall/ck5.2/lib/chicken/11/ chicken.time.import.so ... [debug] loading compiled library /home/matt/data/buildall/ck5.2/lib/chicken/11/chicken.time.import

Re: Guidance requested for debugging import problem.

2021-11-12 Thread felix . winkelmann
> On Fri, Nov 12, 2021 at 3:47 AM wrote: > > > > 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 pr

Re: Guidance requested for debugging import problem.

2021-11-12 Thread Matt Welland
On Fri, Nov 12, 2021 at 3:47 AM wrote: > > 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 read

Re: Guidance requested for debugging import problem.

2021-11-12 Thread felix . winkelmann
> 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 dep

Re: Guidance requested for debugging import problem.

2021-11-11 Thread 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

Guidance requested for debugging import problem.

2021-11-11 Thread Matt Welland
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