problem in running glibc-2.2.5 testsuite

[chandrakumar@chandrakumar.in]

Hi,

I am working with the gnu toolchain of versions as follows:
- binutils of version 2.10.1
- gcc of version 2.95.3
- glibc of version 2.2.5

The above toolchain is ported for a RISC architecture.

I have installed binutils and gcc successfully. I have built glibc with
using the installed cross-compiler. But on running the glibc testsuite via
make check, I encounter the following error:

target-linux-gcc tst-gettext.c -c -O2 -Wall -Winline -Wstrict-prototypes
-Wwrite-strings -g   -DTESTSTRS_H=\"/home/build_glibc/intl/msgs.h\"
-I../include -I. -I/home/build_glibc/intl -I.. -I../libio
-I/home/build_glibc .... 
....
....
-o /home/build_glibc/intl/tst-gettext.o
In file included from tst-gettext.c:37:
/home/build_glibc/intl/msgs.h:16: `msgstr' undeclared here (not in a
function)
/home/build_glibc/intl/msgs.h:16: initializer element is not constant
/home/build_glibc/intl/msgs.h:16: (near initialization for
`msgs[3].msgstr')
/home/build_glibc/intl/msgs.h:16: parse error before string constant
/home/build_glibc/intl/msgs.h:18: warning: excess elements in struct
initializer
/home/build_glibc/intl/msgs.h:18: warning: (near initialization for
`msgs[3]')
/home/build_glibc/intl/msgs.h:75: `msgstr' undeclared here (not in a
function)
/home/build_glibc/intl/msgs.h:75: initializer element is not constant
/home/build_glibc/intl/msgs.h:75: (near initialization for
`msgs[23].msgstr')
/home/build_glibc/intl/msgs.h:75: parse error before string constant
/home/build_glibc/intl/msgs.h:77: warning: excess elements in struct
initializer
/home/build_glibc/intl/msgs.h:77: warning: (near initialization for
`msgs[23]')
/home/build_glibc/intl/msgs.h:103: `msgstr' undeclared here (not in a
function)
/home/build_glibc/intl/msgs.h:103: initializer element is not constant
/home/build_glibc/intl/msgs.h:103: (near initialization
for`msgs[36].msgstr')

I couldn't find the cause for the above errors and warnings. Could someone
help me out to find any reference regarding this.

Thank you,
Chandra Kumar R.