On Sat, 1 Nov 1997, Tom Dye wrote:
Alternatively, you can compile your own GPC. That's not that hard
So, I took this option. But on the following command, lots of
things
happen (all magic to me) then it ends.
make CFLAGS=-O3 LANGUAGES=pascal
The output of the second go-round, after the initial failure gives this output:
rm -f tmplibgcc2.a for name in _muldi3 _divdi3 _moddi3 _udivdi3 _umoddi3 _negdi2 _lshrdi3 _ashldi3 _ashrdi3 _ffsdi2 _udiv_w_sdiv _udivmoddi4 _cmpdi2 _ucmpdi2 _floatdidf _floatdisf _fixunsdfsi _fixunssfsi _fixunsdfdi _fixdfdi _fixunssfdi _fixsfdi _fixxfdi _fixunsxfdi _floatd ixf _fixunsxfsi _fixtfdi _fixunstfdi _floatditf __gcc_bcmp _varargs _eprintf _op_new _op_vnew _new_handler _op_delete _op_vdel _bb _shtab _clear_cache _trampoline __main _exit _ctors _eh _pure; \ do \ echo ${name}; \ ./xgcc -B./ -O2 -DIN_GCC -DUSE_GNULIBC_1 -O3 -I./include -fPIC -g1 -I. -I. -I./config -c -DL${name} \ ./libgcc2.c -o ${name}.o; \ if [ $? -eq 0 ] ; then true; else exit 1; fi; \ ar rc tmplibgcc2.a ${name}.o; \ rm -f ${name}.o; \ done _muldi3
This is what the ending looks like:
/tmp/cca12043.i:1: numeric constant with no digits /tmp/cca12043.i:1: numeric constant with no digits
[...]
Actually, this is the location where your newly built GCC (_not_ GPC) is first put into action. Since you built it yourself, there can be no libc problems.
It seems the assembler has trouble with the assembly produced by GCC.
Can you tell me what versions of GCC and binutils you have installed? i.e. what's the output of `as -v' and `gcc -v' ?
JanJaap
--- With sufficient thrust, pigs fly just fine. However, this is not necessarily a good idea. It is hard to be sure where they are going to land, and it could be dangerous sitting under them as they fly overhead. -- RFC1925.