public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Alessandro Pinto" <apinto@parades.rm.cnr.it>
To: "Jonathan Larmour" <jlarmour@redhat.co.uk>
Cc: <ecos-discuss@sourceware.cygnus.com>
Subject: [ECOS] Configuration tool problem
Date: Thu, 01 Jun 2000 03:02:00 -0000	[thread overview]
Message-ID: <008a01bfcc15$5ae24120$28259296@parades.rm.cnr.it> (raw)
In-Reply-To: <3935726B.9AF476BC@redhat.co.uk>

Thank you a lot for your help yesterday, I compiled the gcc and all was ok.
Now I need to create a the ecos RTOS to use the library and link it.
When I try to run the configuration tool, the compilation results in the
follow error:

arm-elf-gcc -c  -I//C/ecoslib/prova_install/include -I//C/PROGRA~1/REDHAT~1/
eCos/packages/hal/arm/arch/v1_3_1 -I//C/PROGRA~1/REDHAT~1/eCos/packages/hal/
arm/arch/v1_3_1/src -I//C/PROGRA~1/REDHAT~1/eCos/packages/hal/arm/arch/v1_3_
1/tests -I. -I//C/PROGRA~1/REDHAT~1/eCos/packages/hal/arm/arch/v1_3_1/src/ -
mcpu=arm7tdmi -Wall -Wpointer-arith -Wstrict-prototypes -Winline -Wundef -Wo
verloaded-virtual -g -O2 -ffunction-sections -fdata-sections -fno-rtti -fno-
exceptions -fvtable-gc -finit-priority -Wp,-MD,src/context.tmp -o
src/hal_arm_arch_context.o
file://C/PROGRA~1/REDHAT~1/eCos/packages/hal/arm/arch/v1_3_1/src/context.S
file://C/PROGRA~1/REDHAT~1/eCos/packages/hal/arm/arch/v1_3_1/src/context.S:
Assembler messages:
file://C/PROGRA~1/REDHAT~1/eCos/packages/hal/arm/arch/v1_3_1/src/context.S:1
14: Error: undefined symbol CPSR_IRQ_DISABLE in operation
file://C/PROGRA~1/REDHAT~1/eCos/packages/hal/arm/arch/v1_3_1/src/context.S:1
14: Error: undefined symbol CPSR_FIQ_DISABLE in operation
file://C/PROGRA~1/REDHAT~1/eCos/packages/hal/arm/arch/v1_3_1/src/context.S:8
5: Error: Internal_relocation (type 187) not fixed up (OFFSET_IMM)
file://C/PROGRA~1/REDHAT~1/eCos/packages/hal/arm/arch/v1_3_1/src/context.S:1
16: Error: Internal_relocation (type 187) not fixed up (OFFSET_IMM)
make[1]: *** [src/context.o.d] Error 1
make[1]: Leaving directory `/c/ecoslib/prova_build/hal/arm/arch/v1_3_1'
make: *** [build] Error 2

Can you help me?

Bye

AP

  reply	other threads:[~2000-06-01  3:02 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-05-29 18:27 [ECOS] about timeslice and same priority thread switch yyl
2000-05-30 14:47 ` Jonathan Larmour
2000-05-30 18:40   ` yyl
2000-05-31 13:13     ` Jonathan Larmour
2000-06-01  3:02       ` Alessandro Pinto [this message]
2000-06-01  8:03         ` [ECOS] Re: Configuration tool problem Jonathan Larmour
2000-06-01  8:57           ` Alessandro Pinto
2000-06-01  9:08             ` Jonathan Larmour
2000-06-01 22:31       ` [ECOS] about timeslice and same priority thread switch zhang
2000-06-02 11:12         ` Jonathan Larmour
2001-01-02 19:14 [ECOS] Configuration Tool problem Xavier Wang
2001-01-03  4:27 ` Julian Smart
2001-01-03  4:58 ` Bart Veer
2001-10-25 16:39 [ECOS] Configuration tool problem Andreas Savvides
2001-10-26  7:46 ` Julian Smart
2001-10-26  8:06   ` Trenton D. Adams

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='008a01bfcc15$5ae24120$28259296@parades.rm.cnr.it' \
    --to=apinto@parades.rm.cnr.it \
    --cc=ecos-discuss@sourceware.cygnus.com \
    --cc=jlarmour@redhat.co.uk \
    /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).