BFD internal error. Bug? Size limit?

[Haroldo Stenger]

Hello,

I'm having serious trouble, and am clueless:

I'm using FlagShip, which generates C code from dos clipper code, and compiles
it with gcc. I't worked fine for months. Unexpectedly, it started giving an
error:

FlagShip PRO (unlimited users)
(c) Copyright 1989..2001 by multisoft GmbH Munich/Germany
C compiler and linker phase:
/usr/i486-suse-linux/bin/ld: BFD internal error, aborting at elf32-i386.c line
1598 in elf_i386_relocate_section

/usr/i486-suse-linux/bin/ld: Please report this bug.

collect2: ld returned 1 exit status

As a means of showing command line parameters to ld, this is the ps output while
the compile process was running:

haroldo    791  1.0  0.1  1120  504 pts/0    S    13:09   0:00 cc -DFGSLINUX
-DFGSLINUXELF -I/usr/include/ncur194 -fwritable-strings -fPIC -I/usr/include
apresent_m.c -o farmas ref.o -L/lib -L/usr/lib farmas.a /usr/lib/dynFlagShip.o
-lFlagShip -lncur194 -lm -s

haroldo    795  0.0  0.1  1092  464 pts/0    S    13:09   0:00
/usr/lib/gcc-lib/i486-suse-linux/2.95.2/collect2 -m elf_i386 -dynamic-linker
/lib/ld-linux.so.2 -o farmas -s /usr/lib/crt1.o /usr/lib/crti.o
/usr/lib/gcc-lib/i486-suse-linux/2.95.2/crtbegin.o -L/lib -L/usr/lib
-L/usr/lib/gcc-lib/i486-suse-linux/2.95.2 -L/usr/i486-suse-linux/lib
/tmp/ccdKEb0J.o ref.o farmas.a /usr/lib/dynFlagShip.o -lFlagShip -lncur194 -lm
-lgcc -lc -lgcc /usr/lib/gcc-lib/i486-suse-linux/2.95.2/crtend.o /usr/lib/crtn.o

haroldo    796 93.5 24.0 63744 63020 pts/0   R    13:09   0:01
/usr/i486-suse-linux/bin/ld -m elf_i386 -dynamic-linker /lib/ld-linux.so.2 -o
farmas -s /usr/lib/crt1.o /usr/lib/crti.o
/usr/lib/gcc-lib/i486-suse-linux/2.95.2/crtbegin.o -L/lib -L/usr/lib
-L/usr/lib/gcc-lib/i486-suse-linux/2.95.2 -L/usr/i486-suse-linux/lib
/tmp/ccdKEb0J.o ref.o farmas.a /usr/lib/dynFlagShip.o -lFlagShip -lncur194 -lm
-lgcc -lc -lgcc /usr/lib/gcc-lib/i486-suse-linux/2.95.2/crtend.o
/usr/lib/crtn.oroot       797  0.0  0.3  2472  908 pts/1    R    13:09   0:00 ps
axu


The farmas.a file is a ~100 MB ar-format file. The executable, before the
compiling process started yielding error, sized ~70MB.

Am I crossing a size limit? Is this ant king of buffer overflow?

I don't remember any significant change in what I was doing, which could explain
the error. As I said above, I am clueless, and in a hurry.

I would greatly apreciate any help.

Haroldo Stenger.