> 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 understanding the problem. I have added -M to the compilation rules for the modules and removed the "uses" declaration of m1.import and the example still seems to work. -M includes the registration code in the binary, so that the module is visible at runtime. Perhaps this would help getting rid of the seprate *.import units. felix
