From: Christian Plessl <cplessl@ee.ethz.ch>
To: Jochen Hagemann <jh@genologic.de>
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] i386 target crashes after download
Date: Fri, 19 Jan 2001 08:25:00 -0000 [thread overview]
Message-ID: <5.0.2.1.0.20010119172100.00a7a1e0@imap.ee.ethz.ch> (raw)
In-Reply-To: <3A6856A6.F024D9B5@genologic.de>
>
>I built the loader with the following script in a directory named "stub"
>--
>export ECOS_REPOSITORY=/opt/ecos/ecos-1.3.1/packages
>export PATH=/tools/H-i686-pc-linux-gnu/bin:$PATH
>ECOS_TOOLS=/opt/ecos-1.3.1/tools/bin
>$ECOS_TOOLS/ecosconfig new pc stubs
>$ECOS_TOOLS/ecosconfig check
>$ECOS_TOOLS/ecosconfig tree
>make
>--
>...and got those messages:
>
>7 conflict(s) resolved:
>CYGBLD_BUILD_GDB_STUBS:
> Requires constraint not satisfied: CYG_HAL_STARTUP == "FLOPPY"
>CYGSEM_HAL_ROM_MONITOR:
> Requires constraint not satisfied: !CYGDBG_HAL_DEBUG_GDB_CTRLC_SUPPORT
>CYGBLD_BUILD_GDB_STUBS:
> Requires constraint not satisfied: CYGSEM_HAL_ROM_MONITOR
>CYGBLD_BUILD_COMMON_GDB_STUBS:
> Requires constraint not satisfied: CYGDBG_HAL_DEBUG_GDB_INCLUDE_STUBS
>CYGBLD_BUILD_GDB_STUBS:
> Requires constraint not satisfied: CYGBLD_BUILD_COMMON_GDB_STUBS
>CYGBLD_BUILD_GDB_STUBS:
> Requires constraint not satisfied: !
> CYGDBG_HAL_COMMON_INTERRUPTS_SAVE_MINIMUM_CONTEXT
>CYGBLD_BUILD_GDB_STUBS:
> Requires constraint not satisfied: ! CYGDBG_HAL_COMMON_CONTEXT_SAVE_MINIMUM
>Target: pc
>Template: stubs
>No conflicts
>...
>(finally :-) build finished
Ok,this looks reasonable.
>When I built the library in a different directory named "target" with
>--
>export ECOS_REPOSITORY=/opt/ecos/ecos-1.3.1/packages
>export PATH=/tools/H-i686-pc-linux-gnu/bin:$PATH
>ECOS_TOOLS=/opt/ecos-1.3.1/tools/bin
>$ECOS_TOOLS/ecosconfig new pc
>$ECOS_TOOLS/ecosconfig check
>$ECOS_TOOLS/ecosconfig tree
>make
>--
>...I got those messages:
>
>1 conflict(s) resolved:
>CYGSEM_HAL_I386_PC_STARTUP_RAM:
> Requires constraint not satisfied:
> !CYGIMP_HAL_COMMON_INTERRUPTS_USE_INTERRUPT
>Target: pc
>Template: default
>2 conflict(s):
>CYGSEM_HAL_I386_PC_STARTUP_RAM:
> Requires constraint not satisfied: CYGDBG_HAL_DEBUG_GDB_INCLUDE_STUBS
>CYGSEM_HAL_I386_PC_STARTUP_RAM:
> Requires constraint not satisfied: CYGDBG_HAL_DEBUG_GDB_BREAK_SUPPORT
>5 conflict(s) resolved:
>CYGSEM_HAL_I386_PC_STARTUP_RAM:
> Requires constraint not satisfied: CYGDBG_HAL_DEBUG_GDB_INCLUDE_STUBS
>CYGDBG_HAL_DEBUG_GDB_CTRLC_SUPPORT:
> Requires constraint not satisfied: !CYGDBG_HAL_DEBUG_GDB_BREAK_SUPPORT
>CYGSEM_HAL_I386_PC_STARTUP_RAM:
> Requires constraint not satisfied: CYGDBG_HAL_DEBUG_GDB_BREAK_SUPPORT
>CYGDBG_HAL_DEBUG_GDB_CTRLC_SUPPORT:
> Requires constraint not satisfied: !CYGDBG_HAL_DEBUG_GDB_BREAK_SUPPORT
>CYGSEM_HAL_I386_PC_STARTUP_RAM:
> Requires constraint not satisfied: CYGDBG_HAL_DEBUG_GDB_BREAK_SUPPORT
>...
>(finally :-) build finished
>I could get rid of the conflicts by editing the ecos.ecc file.
This is strange, I do not have any conflicts that need to be resolved by
hand.. What version of ecos you are using? The latest CVS snapshot? Your
install path of ecos looks like you are using ecos-1.3.1 release, are you?
My experience was, that upgrading, to the latest cvs version solves a lot
of problems..
Cheers,
Chris
--
Christian Plessl <cplessl@ee.ethz.ch>
next prev parent reply other threads:[~2001-01-19 8:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-18 9:40 Jochen Hagemann
2001-01-18 13:51 ` Jonathan Larmour
2001-01-19 1:41 ` Jochen Hagemann
2001-01-19 2:03 ` Christian Plessl
[not found] ` <5.0.2.1.0.20010119105711.00a90510@imap.ee.ethz.ch>
2001-01-19 7:40 ` Jochen Hagemann
2001-01-19 8:25 ` Christian Plessl [this message]
2001-01-19 3:18 Christian Plessl
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5.0.2.1.0.20010119172100.00a7a1e0@imap.ee.ethz.ch \
--to=cplessl@ee.ethz.ch \
--cc=ecos-discuss@sources.redhat.com \
--cc=jh@genologic.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).