Re: What's up with the CVS sever?

* "MK" == Michael Kifer <kifer(a)cs.sunysb.edu&gt; writes: Michael> Worst of all, when I start xemacs after that it fails to Michael> recognize the Michael> packages in xemacs-packages, even though I have a symbolic link Michael> from xemacs/xemacs-packages to the xemacs-packages directory, Michael> which is a CVS copy of that module. MK> What's that? Haven't seen any such dir or its mention. You set $STAGING in Local.rules (cp Local.rules.template). MK> Isn't it true that all these packages should be in xemacs-packages? MK> So the link from xemacs/xemacs-packages to the packages dir should do the MK> trick (provided that the packages are built correctly, which I am yet to MK> achieve)? Well it would do the trick if the directory structure in the CVS package tree was the same as what XEmacs expects to find, but it isn't. Which is why it would be extremely difficult to run the packages in place from the CVS tree.[1] This is what you are trying to do isn't it? MK> The real problems came when I then ran "make all" in the xemacs-packages MK> directory and got lots of errors. Some of them seem, indeed, to be errors. For MK> instance, After you create a Local.rules from Local.rules.template and edit it to suit your needs, a better target to run would be "make install". MK> make[3]: Entering directory MK> `/home/users/kifer/xemacs-packages/comm/gnus/tm'Makefile:51: MK> ../../XEmacs.rules: No such file or directory Um, './comm/gnus/tm' isn't in my tree (updated 10 minutes ago). MK> The file XEmacs.rules is sitting 3 levels above this, not two. MK> There are many such incorrect include statements in the subdirectories of comm. Where are they exactly? I don't see these errors when I build the packages. MK> xemacs exiting.Cannot open load file: texinfmt MK> make[2]: *** [vm.info] Error 255 MK> make[2]: Leaving directory `/home/users/kifer/xemacs-packages/comm/vm' MK> xemacs exiting.Cannot open load file: advice MK> make[2]: *** [lisp/base64.elc] Error 255 MK> make[2]: Leaving directory `/home/users/kifer/xemacs-packages/comm/w3' MK> xemacs exiting.Cannot open load file: /home/users/kifer/xemacs-packages/comm/gnus/gnus/lisp/auto-autoloads MK> make[2]: *** [expect.elc] Error 255 MK> Generating autoloads for mule-base/char-table.el... MK> Unbalanced parentheses MK> xemacs exiting. MK> make[2]: *** [auto-autoloads.el] Error 255 MK> Generating autoloads for lisp/lookup-entry.el... MK> Unbalanced parentheses MK> xemacs exiting. MK> make[2]: *** [lisp/auto-autoloads.el] Error 255 Hmm, not good. And what's worse is that I don't see any of these errors when I build the packages. Perhaps you got some file corruption when you checked out the xemacs-packages module (it happened to me once). Check one of those files that gave you the 'unbalanced parentheses' error for strange things. If that's the case you'll need to delete your tree and check out the module again. Footnotes: [1] I didn't say "impossible" simply because I have never tried to do this. -- |---<Regards, Steve Youngs>-----------[GnuPG KeyID: 59E4C4B2]---| | XEmacs - It's not just an editor... | | It's a way of life. | |----------------------------------<mailto:youngs＠xemacs.org>---|