From: "James Yates" <j.yates@quartzuk.com>
To: "Santha Kumar" <santhakumar@myw.ltindia.com>,
<ecos-discuss@sources.redhat.com>
Subject: RE: [ECOS] Building errors
Date: Thu, 23 Oct 2003 14:46:00 -0000 [thread overview]
Message-ID: <CB39E7B8FC98924D85DFBED207E4CC9831F92A@ip02.quartzelec.adsl.gxn.net> (raw)
Did you download the tools, i.e compiler suite for the PPC when you downloaded ecos. I expect that this is your problem. If you have downloaded them, make sure the configuration tools is pointing at them , Tools/Paths/Build Tools' menu.
Also if you have been using a different ppc compiler make sure it isn't on your path. I am developing on the SH and had been using a different version of gcc which was on my path. Even though I selected the eCos built gcc in the configuration tool, the old compiler was still being used.
Try adding -v to the front of the compiler flags.
James Yates
-----Original Message-----
From: Santha Kumar [mailto:santhakumar@myw.ltindia.com]
Sent: 23 October 2003 15:29
To: ecos-discuss@sources.redhat.com
Subject: [ECOS] Building errors
Hello
I have downloaded ecos 2.0 from net , Built the tool chain for PPC
and while trying to build the library. I am getting the following error
make -r -C hal/powerpc/arch/v2_0
/ecos-c/DOCUME~1/SANTHA~1/Desktop/eCos/ecos_work/project1_install/include/cyg/hal/ppc_offsets.inc
make[1]: Entering directory
`/ecos-c/DOCUME~1/SANTHA~1/Desktop/eCos/ecos_work/project1_build/hal/powerpc/arch/v2_0'
powerpc-eabi-gcc -msoft-float -mcpu=860 -Wall -Wpointer-arith
-Wstrict-prototypes -Winline -Wundef -Woverloaded-virtual -g -O2
-ffunction-sections -fdata-sections -fno-rtti -fno-exceptions
-fvtable-gc -finit-priority
-I/ecos-c/DOCUME~1/SANTHA~1/Desktop/eCos/ecos_work/project1_install/include
-I/ecos-c/cygwin/opt/ecos/ecos-2.0/packages/hal/powerpc/arch/v2_0
-I/ecos-c/cygwin/opt/ecos/ecos-2.0/packages/hal/powerpc/arch/v2_0/src
-I/ecos-c/cygwin/opt/ecos/ecos-2.0/packages/hal/powerpc/arch/v2_0/tests
-I. -Wp,-MD,ppc_offsets.tmp -o hal_mk_defs.tmp -S
/ecos-c/cygwin/opt/ecos/ecos-2.0/packages/hal/powerpc/arch/v2_0/src/hal_mk_defs.c
make[1]: Leaving directory
`/ecos-c/DOCUME~1/SANTHA~1/Desktop/eCos/ecos_work/project1_build/hal/powerpc/arch/v2_0'
cc1: unrecognized option `-Woverloaded-virtual'
make: Leaving directory
`/ecos-c/DOCUME~1/SANTHA~1/Desktop/eCos/ecos_work/project1_build'
cc1: unrecognized option `-fno-rtti'
cc1: unrecognized option `-fvtable-gc'
cc1: unrecognized option `-finit-priority'
make[1]: ***
[/ecos-c/DOCUME~1/SANTHA~1/Desktop/eCos/ecos_work/project1_install/include/cyg/hal/ppc_offsets.inc]
Error 1
make: *** [build] Error 2
Could any body instruct me any way out for this error. Since I am new
to eCos I am not getting a path to proceed .
Regards
Santha kumar
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss
next reply other threads:[~2003-10-23 14:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-23 14:46 James Yates [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-10-23 14:30 Santha Kumar
2003-10-23 14:25 Santha Kumar
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=CB39E7B8FC98924D85DFBED207E4CC9831F92A@ip02.quartzelec.adsl.gxn.net \
--to=j.yates@quartzuk.com \
--cc=ecos-discuss@sources.redhat.com \
--cc=santhakumar@myw.ltindia.com \
/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).