powerpc cross error

[Jessica Brown]

Here's the latest cross-compiling error that I have received during the
"make" from RH6.0 Linux to a PowerPC Target:

if [ -f libgcc2.ready ] ; then \
        true; \
else \
        touch libgcc2.ready; \
fi
make[2]: Leaving directory `/build/gcc295/gcc'
make[2]: Entering directory `/build/gcc295/i686-pc-linux-gnu/libiberty'
test x"no" != xyes || \
  /build/gcc295/gcc/xgcc -B/build/gcc295/gcc/
-B/ppcwrs/i686-pc-linux-gnu/bin/
-c -DHAVE_CONFIG_H -g -O2 -I. -I/source/gcc-2.95.1/libiberty/../include
/source/gcc-2.95.1/libiberty/strerror.c -o pic/strerror.o
/build/gcc295/gcc/xgcc -B/build/gcc295/gcc/
-B/ppcwrs/i686-pc-linux-gnu/bin/
-c -DHAVE_CONFIG_H -g -O2 -I. -I/source/gcc-2.95.1/libiberty/../include
/source/gcc-2.95.1/libiberty/strerror.c
/source/gcc-2.95.1/libiberty/strerror.c:461: conflicting types for
`sys_errlist'/usr/include/stdio.h:553: previous declaration of
`sys_errlist'
make[2]: *** [strerror.o] Error 1
make[2]: Leaving directory `/build/gcc295/i686-pc-linux-gnu/libiberty'
make[1]: *** [all-target-libiberty] Error 2
make[1]: Leaving directory `/build/gcc295'
make: *** [cross] Error 2


Here's the line from stdio.h:

/* These variables normally should not be used directly.  The `strerror'

   function provides all the needed functionality.  */
#ifdef  __USE_BSD
extern int sys_nerr;
--> extern __const char *__const sys_errlist[];
#endif
#ifdef  __USE_GNU
extern int _sys_nerr;
extern __const char *__const _sys_errlist[];
#endif

Here's strerror.c:

#ifndef HAVE_SYS_ERRLIST

static int sys_nerr;
--> static const char **sys_errlist;

#else

extern int sys_nerr;
extern char *sys_errlist[];

#endif

------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com