This is the mail archive of the ecos-discuss@sources.redhat.com mailing list for the eCos project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

RE: How to disable GDB STUBS?


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

U CYGHWR_HAL_ARM_DUMP_EXCEPTIONS, new inferred value 0
U CYGDBG_HAL_DEBUG_GDB_INCLUDE_STUBS, new inferred value 1
U CYGDBG_HAL_COMMON_CONTEXT_SAVE_MINIMUM, new inferred value 0
C CYGBLD_BUILD_REDBOOT, "requires" constraint not satisfied:
!CYGINT_HAL_DEBUG_GDB_STUBS || CYGDBG_
HAL_DEBUG_GDB_INCLUDE_STUBS
C CYGBLD_BUILD_REDBOOT, "requires" constraint not satisfied:
!CYGINT_HAL_DEBUG_GDB_STUBS || CYGDBG_
HAL_DEBUG_GDB_BREAK_SUPPORT
C CYGBLD_BUILD_REDBOOT, "requires" constraint not satisfied:
!CYGINT_HAL_DEBUG_GDB_STUBS || CYGDBG_
HAL_DEBUG_GDB_INCLUDE_STUBS
C CYGBLD_BUILD_REDBOOT, "requires" constraint not satisfied:
!CYGINT_HAL_DEBUG_GDB_STUBS || CYGDBG_
HAL_DEBUG_GDB_BREAK_SUPPORT

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

Any suggestions?

Thanks,
Lomesh

-----Original Message-----
From: Bart Veer [mailto:bartv@ecoscentric.com] 
Sent: Tuesday, November 05, 2002 1:35 PM
To: Agarwal, Lomesh
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] How to disable GDB STUBS?


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

    Lomesh> In my redboot_ROM.ecm file I added an entry:
    Lomesh> cdl_option CYGDBG_HAL_DEBUG_GDB_INCLUDE_STUBS {
    Lomesh>     inferred_value 0
    Lomesh> };
    Lomesh> But still all the code under #ifdef
    Lomesh> CYGDBG_HAL_DEBUG_GDB_INCLUDE_STUBS is getting compiled.
    Lomesh> How can I undef it?

Part of the problem may be that the inference engine is changing the
value of this option again. "inferred_value" should be used only for
options that were updated by the inference engine to resolve some
conflict in the configuration. If there are still conflicts in the
configuration then the engine is allowed to reset the value to 1, if
that solves the problem(s).

Instead you should be using a user_value:

    cdl_option CYGDBG_HAL_DEBUG_GDB_INCLUDE_STUBS {
        user_value 1
    }

The inference engine will not override user settings. If there are
conflicts it will try to resolve them some other way, or report the
configuration as invalid.

Bart

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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]