Bug in gcc 4.0.2?

Hello all,

I'm confused at the moment. I work with WinARM Version 20060125. This
Version contained the gcc 4.0.2.

When I try to compile follows then an big endian binary is the result.
Thats expected and correct:

@arm-elf-gcc -c -mcpu=arm7tdmi -T../system_source/TMS470R1B1M-RAM.ld
-T../system_source/reg_map.ld -Wall
-Wextra -Wshadow -Wpointer-arith -Wcast-align -Wsign-compare
-Waggregate-return -Wunused -D RUN_FROM_RAM
-D GCC_ARM7 -I. -I.. -I../include -g -O0 -mbig-endian -v
-Wbad-function-cast -Wstrict-prototypes
-Wmissing-prototypes -Wmissing-declarations
BinFram.c -o BinFram.o


And now my confusion. When I try to compile follows it was created a
little endian binary. And this isn't expected. Is it a bug in the gcc?
The only one difference is that the source file is located in an
underlayed folder.

@arm-elf-gcc -c -mcpu=arm7tdmi -T../system_source/TMS470R1B1M-RAM.ld
-T../system_source/reg_map.ld -Wall
-Wextra -Wshadow -Wpointer-arith -Wcast-align -Wsign-compare
-Waggregate-return -Wunused -D RUN_FROM_RAM
-D GCC_ARM7 -I. -I.. -I../include -g -O0 -mbig-endian -v
-Wbad-function-cast -Wstrict-prototypes
-Wmissing-prototypes -Wmissing-declarations
BinFram/BinFram.c -o BinFram/BinFram.o

I'm very happy for each hint.

Regards,
Karsten