[ECOS] building arm ROM without GDB stubs

Dave Airlie airlied@parthus.com
Mon Jan 15 03:55:00 GMT 2001


Using Cygwin / Windows Configtool I can genearate an .ecc file with no
conflicts but when I compile I get:

rm-elf-gcc -c  -I//D/ecos/fj1_install/include
-I//R/devel/ecos-010112/packages/hal/common/current
-I//R/devel/ecos-010112/packages/hal/common/current/src
-I//R/devel/ecos-010112/packages/hal/common/current/tests
-I. -I//R/devel/ecos-010112/packages/hal/common/current/src/
-mcpu=arm7tdmi -Wall -Wpointer-arith -Wstrict-prototypes -Winline -Wundef
-Woverloaded-virtual -g -O2 -ffunction-sections -fdata-sections -fno-rtti
-fno-exceptions -fvtable-gc -finit-priority -Wp,-MD,src/hal_if.tmp -o
src/hal_common_hal_if.o
//R/devel/ecos-010112/packages/hal/common/current/src/hal_if.c
//R/devel/ecos-010112/packages/hal/common/current/src/hal_if.c:142: #error
" no RESET_ENTRY"
make[1]: *** [src/hal_if.o.d] Error 1
make[1]: Leaving directory `/d/ecos/fj1_build/hal/common/current'
make: *** [build] Error 2

If I add GDB stubs in HAL to my ROM image I can build a library
successfully, I am sure I've done this before has something changed?

I'm using snapshot from 12 January...

Dave.

-- 
      David Airlie, Software Engineer, Parthus Technologies plc.,
       Mary Rosse Centre, National Tech Park, Limerick, Ireland.
   t: +353-61-508116 / f: +353-61-508101 / David.Airlie@parthus.com



More information about the Ecos-discuss mailing list