Re: why was makefile changed to produce this?

[Nick Dokos <nicholas.dokos@hp.com>]

Jude DaShiell <jdashiel@shellworld.net> wrote:

> My bad, I was missing texinfo package and thought that had already been 
> installed.  Once that got installed, everything works as well as it did 
> earlier this year.  If I knew what path that error took, I'd write what 
> might be a better error message for it asking for the texinfo package to 
> be installed.
> 
> 

Here is a useful command that you can use on Debian and Ubuntu systems
in situations like this:

--8<---------------cut here---------------start------------->8---
$ dpkg -S makeinfo
texinfo: /usr/bin/makeinfo
octave3.2-common: /usr/share/octave/3.2.4/m/help/__makeinfo__.m
emacs23-common: /usr/share/emacs/23.1/lisp/textmodes/makeinfo.elc
texinfo: /usr/share/man/man1/makeinfo.1.gz
--8<---------------cut here---------------end--------------->8---

It tells you the packages containing files that match the argument
to the command.

Also, on modern Ubuntu, it is often the case that when you try to
execute a command by hand and it is not found, the system will suggest
the installation of a package:

--8<---------------cut here---------------start------------->8---
$ foo
No command 'foo' found, did you mean:
 Command 'fio' from package 'fio' (universe)
 Command 'goo' from package 'goo' (universe)
 Command 'fop' from package 'fop' (universe)
 Command 'fox' from package 'objcryst-fox' (universe)
 Command 'xoo' from package 'xoo' (universe)
 Command 'zoo' from package 'zoo' (universe)
foo: command not found

$ goo
The program 'goo' is currently not installed.  To run 'goo' please ask your administrator to install the package 'goo'
--8<---------------cut here---------------end--------------->8---

HTH,
Nick

PS I have no idea what the package/command ``goo'' does.