Mail Archives: djgpp/2000/09/20/08:23:06
In article <8q9vhv$dlq$1 AT antares DOT lu DOT erisoft DOT se>,
Martin Stromberg <eplmst AT lu DOT erisoft DOT se> wrote:
>Clark L. Coleman (clc5q AT cobra DOT cs DOT Virginia DOT EDU) wrote:
>: Now, the problem is that:
>
>: gcc -c -g -o foo.o foo.c
>
>: (this is executed from a makefile)
>
>: produces object file FOO.O instead of foo.o. The make terminates,
>: probably because it detects the fact that it failed to produce the
>: target 'foo.o'. Running make again recompiles foo.c into FOO.O again
>: and terminates again.
>
>: Any ideas?
>
>Throw in "-v" in CFLAGS and post the output from make here. This is to
>find out if make or gcc makes the .o upper-case.
>
>
>Right,
>
> MartinS
It turns out that cc1 is getting "divide overflow" errors and
terminating. The FOO.O file is an old one, not being recreated each
time. So, this is another "too big for gcc to handle" problem, I
think, as the file being compiled has really big basic blocks, big
switch statements,long distance branches, etc. Compiles fine in
Solaris, IRIX, etc. environments with gcc 2.8.1 and 2.95.x, but not
with latest 2.95.2 in DJGPP. What next?
Clark
- Raw text -