VM

VM install on Ubuntu 20.04 fails - Outdated usage of ‘bbdb-search’

Asked by Stas Burdan

Hello All,

I am installing VM on Ubuntu 20.04, and it fails with the following message:

stas@captain:~/vm/vm-8.2.0b$ make

"emacs" -batch -q -no-site-file -no-init-file -l ./vm-build.el -f batch-byte-compile vm-pcrisis.el

In toplevel form:
vm-pcrisis.el:86:1:Warning: defcustom for ‘vmpc-conditions’ fails to specify
    type
vm-pcrisis.el:86:1:Warning: defcustom for ‘vmpc-conditions’ fails to specify
    type
vm-pcrisis.el:228:35:Warning: make-face called with 2 arguments, but accepts
    only 1
vm-pcrisis.el:235:31:Warning: make-face called with 2 arguments, but accepts
    only 1
Outdated usage of ‘bbdb-search’
vm-pcrisis.el:1217:28:Error: Variable name missing after &optional
make[1]: *** [Makefile:114: vm-pcrisis.elc] Error 1
make[1]: Leaving directory '/home/stas/vm/vm-8.2.0b/lisp'
make: *** [Makefile:37: all] Error 1

I don't know what BBDB is and looking for the simplest possible work around so I can get VM up
and running. I don't know Lisp, so can't rewrite stuff without steep learning curve.

Thank you in advance!

Question information

Language:
English Edit question
Status:
Solved
For:
VM Edit question
Assignee:
No assignee Edit question
Solved by:
Stas Burdan
Solved:
Last query:
Last reply:
Revision history for this message
Mark Diekhans (markd-kermodei) said : 		#1

It works if built from source:

bzr clone http://bazaar.launchpad.net/~vm/vm/trunk/
cd trunk
autoconf
./configure

make these changes to keep texinfo from generating an error
7091c7091
< @cindex Ulrich M�ller
---
> @cindex Ulrich Muller
 7094c7094
< Robert Widhopf-Fenk, Ulrich M�ller and Uday S Reddy. Other potential members
---
> Robert Widhopf-Fenk, Ulrich Muller and Uday S Reddy. Other potential members

then
make
make install

Revision history for this message
Stas Burdan (sburdan) said : 		#2

Thank you Mark,

this worked. I uninstalled the bbdb Ubuntu package and followed your instructions, had to install few
missing dev tools, but it all worked at the end.

Thank you for the help - VM is up and running! Been using it since 2004