Re: A couple of problems with new module code.

SY> Do you want anything that 'describe-installation' doesn't SY> give? sjt> Do you have an installed 21.5? If so, poke around and see if sjt> there's an old config.h in there somewhere, say in sjt> $archlibdir/include/config.h. OK, that turns out not to be a problem; the build log shows that ellcc does not look in the installed hierarchy. However, I did find another anomoly: "make beta" does not build the modules! I don't understand how you could get the conflict you're seeing from that, though, because make beta does _clean_ the modules. So you shouldn't have a module there to have the wrong value of error-checking. Weird.... I'm not sure what the right fix for the missing dependency in the beta target is. I'm adding ${PROGNAME} as a dependency to the beta target, but it seems like it was deliberately left out. If you do that, then beta: clean all seems equivalent. -- Institute of Policy and Planning Sciences http://turnbull.sk.tsukuba.ac.jp University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN My nostalgia for Icon makes me forget about any of the bad things. I don't have much nostalgia for Perl, so its faults I remember. Scott Gilbert c.l.py