Re: viper build problem [from cvs]
Jens-Ulrik Petersen <petersen(a)kurims.kyoto-u.ac.jp> writes in
xemacs-beta(a)xemacs.org:
[Sorry if this has already been reported: I'm not on xemacs-beta
now.
Sigh. I know the feeling. I'm now unsubscribed from everything not
specifically XEmacs.
I am not a viper user and I don't have time to investigate
further.
I have Poitou and the latest packages from cvs.]
Then we'll have to wait for a confirmation. I don't see a problem.
Did you `cvs update' all the glue files like XEmacs.rules and
package-compile.el?
make[2]: Entering directory `xemacs-packages/wp/viper'
Creating ./_pkg.el
xemacs -no-autoloads -batch -l ../../package-compile.el -- advice cl ring xemacs-base --
viper-cmd.el
Loading xemacs-20/solaris-build/lisp/auto-autoloads...
Loading xemacs-packages/libs/xemacs-base/auto-autoloads...
Wrong type argument: stringp, nil
xemacs exiting.
make[2]: *** [viper-cmd.elc] Error 255
make[2]: Leaving directory `xemacs-packages/wp/viper'
make[1]: *** [all] Error 2
I cannot duplicate this.