www.delorie.com/gnu/docs/gcc/gnat_ug_64.html   search  
Buy the book!

Untitled Document

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

4.4 Binder Error Message Control

The following switches provide control over the generation of error messages from the binder:

Verbose mode. In the normal mode, brief error messages are generated to `stderr'. If this switch is present, a header is written to `stdout' and any error messages are directed to `stdout'. All that is written to `stderr' is a brief summary message.

Generate brief error messages to `stderr' even if verbose mode is specified. This is relevant only when used with the ^-v^/REPORT_ERRORS=VERBOSE^ switch.

Limits the number of error messages to n, a decimal integer in the range 1-999. The binder terminates immediately if this limit is reached.

Renames the generated main program from main to xxx. This is useful in the case of some cross-building environments, where the actual main program is separate from the one generated by gnatbind.

Suppress all warning messages.

Treat any warning messages as fatal errors.

The binder performs a number of consistency checks including:

Normally failure of such checks, in accordance with the consistency requirements of the Ada Reference Manual, causes error messages to be generated which abort the binder and prevent the output of a binder file and subsequent link to obtain an executable.

The ^-t^/NOTIME_STAMP_CHECK^ switch converts these error messages into warnings, so that binding and linking can continue to completion even in the presence of such errors. The result may be a failed link (due to missing symbols), or a non-functional executable which has undefined semantics. This means that ^-t^/NOTIME_STAMP_CHECK^ should be used only in unusual situations, with extreme care.

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

  webmaster     delorie software   privacy  
  Copyright 2003   by The Free Software Foundation     Updated Jun 2003