[ < ] | [ > ] |  | [ << ] | [ Up ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

### 1.6.6 Configuration Related Errors

The source code distribution of `avram` incorporates a flexible configuration script allowing it to be installed on a variety of platforms. Not all platforms allow support for all features. It is also anticipated that new features may be added to `avram` from time to time. Some problems may therefore occur due to features not being supported at your site for either of these reasons. The following error messages are relevant to these situations.

`unsupported hook`

  If it’s not simply due to an application programming error (Application Programming Errors) this message may be the result of trying to use an application that requires a newer version of `avram` than the one installed, even though applications should avoid this problem by checking the version number at run time. If this is the reason, the solution would be to install the latest version.

`application-name: I need avram linked with foo, bar and baz.`

  A message of the this form indicates that a new installation may be needed. At this writing (11/11/1), `avram` may report this message with respect to `libexpect5.32`, `tcl8.3`, and `libutil` if any of the ‘`-i`’, ‘`-t`’, or ‘`-s`’ options is used on a system where not all of these libraries were detected when `avram` was installed from a source distribution. (See Parameter Mode Options.) Because `avram` is useful even without interactive applications, these libraries are not considered absolute prerequisites by the configuration script.

`avram: can't emulate version version`

  The ‘`--emulation=version`’ option obviously won’t work if the requested version is newer than the installed version, or if it is not a valid version number (General Options). When that happens, this message is printed instead and `avram` terminates.

`avram: multiple version specifications`

  The ‘`--emulation=version`’ option can be used at most once on a command line. This message is printed if it is used more than once. If you only typed it once and got this message, check your aliases and wrapper scripts before reporting a bug.

`avram: unrecognized option: option-name`

  may mean that a command line option has been misspelled, or may be another sign of an obsolete version of `avram`. This message will be followed by a usage summary similar to that of the ‘`--help`’ option. (General Options).

`application-name: warning: search paths not supported`

  If the ‘`argz.h`’ header file was not detected during configuration, `avram` will not be able to support search paths in the `AVMINPUTS` environment variable (Environment). This message is a warning that the environment variable is being ignored. If the warning is followed by an i/o error (i/o Errors), the latter may be due to a file being in a path that was not searched for this reason. A workaround is to specify the full path names of all input files outside the current working directory. If you don’t need search paths, you can get rid of this message by undefining `AVMINPUTS`.

[ < ] | [ > ] |  | [ << ] | [ Up ] | [ >> ] |  |  |  |  | [Top] | [Contents] | [Index] | [ ? ]

This document was generated on November 8, 2012 using texi2html 1.82.