[ECOS] How to disable GDB STUBS?

Bart Veer bartv@ecoscentric.com
Wed Nov 6 14:49:00 GMT 2002

>>>>> "Lomesh" == Agarwal, Lomesh <lomesh.agarwal@intel.com> writes:

    Lomesh> I changed inferred value to user value and now inferrence engine is
    Lomesh> getting conflicts. Here is the output:

    Lomesh> U CYGHWR_HAL_ARM_DUMP_EXCEPTIONS, new inferred value 0
    Lomesh> U CYGDBG_HAL_DEBUG_GDB_INCLUDE_STUBS, new inferred value 1
    Lomesh> U CYGDBG_HAL_COMMON_CONTEXT_SAVE_MINIMUM, new inferred value 0
    Lomesh> C CYGBLD_BUILD_REDBOOT, "requires" constraint not satisfied:
    Lomesh> C CYGBLD_BUILD_REDBOOT, "requires" constraint not satisfied:

    Lomesh> Unable to generate build tree, this configuration still contains
    Lomesh> conflicts.
    Lomesh> Either resolve the conflicts or use --ignore-errors
    Lomesh> make: *** No targets specified and no makefile found.  Stop.

    Lomesh> Any suggestions?

Looking at the CDL constraints, the configuration you are after
(RedBoot without gdb stubs) is not currently supported. If you want to
build RedBoot (CYGBLD_BUILD_REDBOOT) and if the architectural HAL (or
possibly variant or platform HAL) provides the necessary support
(CYGINT_HAL_DEBUG_GDB_STUBS) then the generic stubs code in the
common HAL package (CYGDBG_HAL_DEBUG_GDB_INCLUDE_STUBS) is needed.

Changing this would require modifications to RedBoot itself, and
appropriate adjustments to the CDL. These would probably take the form
of a new RedBoot configuration option or component that controls
whether or not RedBoot should be built with gdb stubs functionality.
The requires constraint could then be moved from CYGBLD_BUILD_REDBOOT
to the new option, and the user could then disable that option. I do
not know how much of RedBoot would be affected by such a change.


Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss

More information about the Ecos-discuss mailing list