This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
RE: Insight build error in the gdb for mips simulator
- From: "Dave Korn" <dave dot korn at artimi dot com>
- To: <neuwald at inf dot ufsc dot br>,<gdb at sources dot redhat dot com>
- Date: Tue, 3 May 2005 13:07:10 +0100
- Subject: RE: Insight build error in the gdb for mips simulator
----Original Message----
>From: neuwald@inf.ufsc.br
>Sent: 02 May 2005 15:28
>> Hi,
>>
>> I'm building tools for run application on mips simulator. I compiled
>> binutils and gcc in accordance with:
>> http://ecos.sourceware.org/tools/win-mips-tx39-elf.html. I compiled
>> insight 5.1a and when I used make utility, I got the following error:
>> make[3]: Entering directory `/tmp/build/gdb/sim/igen'
>> gcc -c -g -O2 -I. -I/src/gdb/insight-5.1a/sim/igen
>> -I/src/gdb/insight-5.1a/sim /igen/../../include -O0
>> /src/gdb/insight-5.1a/sim/igen/lf.c
>> /src/gdb/insight-5.1a/sim/igen/lf.c:261:27: missing terminating "
>> character /src/gdb/insight-5.1a/sim/igen/lf.c: In function
>> `lf_print__gnu_copyleft': /src/gdb/insight-5.1a/sim/igen/lf.c:264:
>> error: parse error before "Copyright"
>> /src/gdb/insight-5.1a/sim/igen/lf.c:264: error: syntax error at '@'
>> token /src/gdb/insight-5.1a/sim/igen/lf.c:266: error: `you' undeclared
>> Can anybody help me how to solve this error?
>> Regards,
>> Evandro
This was fixed some time ago: you're using very old versions of the
software.
Mon Jun 3 16:04:31 2002 UTC (2 years, 11 months ago) by rth
http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/sim/igen/lf.c.diff?r1=1.1&r
2=1.2&cvsroot=src&f=h
It's because old compilers used to allow you to write a string in C that
extended across multiple lines without requiring you to escape the line-ends
to mark it as a continuation. That style of string has been depracated for
some time now; you need to either backslash-quote the line ends, or place
closing quotes at the end of each line and opening quotes at the start and
allow the ANSI-string-concatenation rule to take care of it. So you're
seeing this problem only because you're using a more modern version of the
compiler to try and build old code. Anyway, take a look at the patch as
shown above and you'll see how to fix it.
cheers,
DaveK
--
Can't think of a witty .sigline today....