"Stephen J. Turnbull" <stephen(a)xemacs.org> writes:
This _could_ be either packaging issues (sorry, Norbert, but this is
the kind of thing that could happen if we're missing a depend or
something)
No prob. What would you suggest, build a new version of the package
just to decrease the probability of this kind of error? I checked out
a new tree and did basic tests. The sequence
make autoloads && cd xemacs-packages/net-utils && make
gets through, so everything seems to be visible at build-time.
or more byte compiler/interpreter lossage.
norbert.