EFS depends on VM in packages [Was: Build failures with ...]

Vin> The last time I built the packages (2/17), here's what I Vin> found: Vin> 1. Yoshiki's patch fixed the "Invalid read syntax" errors. Vin> 2. I still got the efs build problem: While compiling Vin> toplevel forms in file Vin> /usr/local/build/xemacs-packages-2000-02-17/libs/efs/efs-vm.el: Vin> !! File error (("Cannot open load file" "vm")) Done ms> I'm not sure this means me. EFS has: ms> REQUIRES = xemacs-base vm dired ms> So it does need VM, at least during compilation. When did this happen? (Just out of curiosity; I did not run into this when I built from scratch a couple of months ago.) I don't think this is Michael's problem, although there may be a circular dependency there (even though VM's REQUIRES don't include EFS: it may be that dependencies on EFS don't need to be stated, see the comment in the toplevel package Makefile). VM does not supply a vm.el file; it gets built. So VM must be built before EFS. I think you should be able to do this automatically as long as you have VM in the package tree, by make'ing from the toplevel (I did this from scratch about two months ago on a completely clean machine with no XEmacs installed at all, just a full CVS HEAD (ie, 21.2) source hierarchy and a full package source hierarchy; this requires tweaking some lower-level Makefiles in xemacs-packages). But I don't really understand those Makefiles and package-compile.el. If you want, I will zap those hierarchies and try it again sometime this week or early next, but I can't promise when. -- University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Institute of Policy and Planning Sciences Tel/fax: +81 (298) 53-5091 _________________ _________________ _________________ _________________ What are those straight lines for? "XEmacs rules."