Hello,
> hal_mk_defs is somewhat special. Look at the CDL in hal/arm/arch/...
>
> make -priority 1 {
> arm.inc : <PACKAGE>/src/hal_mk_defs.c
> $(CC) $(ACTUAL_CFLAGS) $(INCLUDE_PATH) -Wp,-MD,arm.tmp -o
hal_mk_defs.tmp -S $<
> fgrep .equ hal_mk_defs.tmp | sed s/#// > $@
> @echo $@ ": \\" > $(notdir $@).deps
> @tail -n +2 arm.tmp >> $(notdir $@).deps
> @echo >> $(notdir $@).deps
> @rm arm.tmp hal_mk_defs.tmp
> }
>
> It is probably worth figuring out what is actually going wrong. No
> error message from gcc might mean gcc is actually working O.K. and you
> have a silly problem with fgrep, sed, tail, etc..
...
Building eCos and tests for target ea2468 with the kernel template works
fine for me using the 2008-12-13 arm-eabi toolchain under the latest
Cygwin. I set CYGBLG_GLOBAL_COMMAND_PREFIX == "arm-eabi" and removed
"-mno-short-load-words" from CYGBLG_GLOBAL_CFLAGS. I note that you have
further modified the compilation flags. The flags should look something
like this:
-finline-limit=7000 -mcpu=arm7tdmi -Wall -Wpointer-arith -Wstrict-prototypes
-Winline -Wundef -g -O2 -ffunction-sections -fdata-sections -fno-exceptions
Also, check that "arm-eabi-gcc" works from a bash prompt and that you
have "fgrep" and "sed" installed.
John Dallaway
I have the precompiled arm-elf toolchain and the precompiled arm-eabi
toolchain from the eCos homepage installed at the same time. I use to
the newest Cygwin version. While the arm-elf toolchain builds the target
ea2468 without any problems, the arm-eabi toolchain fails with described
error message. Because the build works fine with the arm-elf toolchain I
cannot imagine that it is a issue related to my Cygwin installation. If
there would be any problem with fgrep, sed, tail then also the build
with arm-elf toolchain would fail.
I tried to build a simple test.c file from command line:
arm-elf-gcc -c test.c -o test.o
arm-eabi-gcc -c test.c -o test.o
While the arm-elf-gcc printed a warning "no newline at end of file" and
created an test.o file, the arm-eabi-gcc did not print this warning nor
did it produce an test.o file.
This is the same problem like described in this message:
http://ecos.sourceware.org/ml/ecos-discuss/2008-11/msg00075.html
So I'am not the only one with this problem.
Regards, Uwe
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
