Compiler and Linker Problems

• Unresolved external references to _init_db when linking with the production libraries.

  The symbolic constant NO_DEBUG_CODE has not been defined. See Chapter 52, "Preparing Your Application for Distribution," for information about using the production libraries.

• Unresolved external references to _fexitfp and _finitfp when linking with the development libraries.

  The symbolic constant NO_DEBUG_CODE has been declared or has been set on the compile line (e.g., -DNO_DEBUG_CODE). This constant is not required when linking with the development libraries.

  If you linked with the Vermont Views production libraries instead of the development libraries, and you still get a linker error about unresolved externals _finitfp and _fexitfp, you are including header file vv_debug.h in the application's main module. If it is absolutely necessary to include vv_debug.h there, then surround it with conditional code as follows:

    #ifndef NO_DEBUG_CODE

    #include <vv_debug.h>

    #endif

• Symbol redefinition warnings or duplicate symbol declaration errors.

  This is caused by #including vv_main.h in the main file and again in separate files for your sub-routines.

• Unresolved external references to Vermont Views functions.

  You forgot to specify the Vermont Views library in the link statement, or you forgot to #include vv_main.h in your main module.

• Linker error "Fixup offset exceeds field width" or "Fixup overflow" (PCDOS or XENIX only)

  This is always the result of trying to link modules compiled using different memory models. For example, trying to link a program compiled with the small model with a library compiled with the large model produces this error.

  Often this error is caused by specifying the switches in the wrong position in the compile statement such that the compiler ignores them and defaults to the small memory model. It can also be caused by failing to specify the memory model in the compile statement.