Variables for ./configure

The configure program uses the following shell variables to change various defaults. Another method is simply to edit the `nana-config.h' file. Most of these values should be auto detected, so you can ignore this section until your need to save a few bytes of store by using `asm("hlt")' instead of a call to `abort()'.

DI_MAKE_VALID_BREAKPOINT

This text is inserted when the `DI.h' library needs to set a breakpoint in the generated code. It should ideally update all variables which being kept in registers etc so that gdb gets the correct values for each variable. Possible values include:

1. `asm("nop")' -- a single `nop' instruction to set the breakpoint at. This is the default.
2. `_vi = 0' -- where `_vi' is a global volatile int.
3. `_vi = (exprn)' -- where exprn is the expression we are checking for this assertion.
4. `/* nothing */' -- nothing at all, this means the breakpoint will be set at the start of the next statement which works most of the time. However for some examples this will do the wrong thing.

DL_MAKE_VALID_BREAKPOINT

Used for the same purpose as `DI_MAKE_VALID_BREAKPOINT' for `DL.h'. It also defaults to `asm("nop")'.

I_DEFAULT_HANDLER

The code called when `I.h' detects an error.

asm("hlt")

Some machines use a `hlt' instruction.

asm("stp")

And other machines use a `stp' instruction.

abort()

Or we could use a call to `abort' which is at least standard C. On some machines this is significantly larger than a single `hlt' instruction.

restart()

Or a call to a function which attempts to restart the system.

ALWAYS_INCLUDE_MALLOC

This is a dodgey for some versions of Linux which don't seem to include `malloc' when you include `stdio.h' and use `print'. This causes problems for `gdb' since it uses `malloc' in the executable to implement parts of its functionality. This kludge should be removed!

Go to the first, previous, next, last section, table of contents.