This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
cross-compiling libiberty in gcc-3.4
- From: Bernardo Innocenti <bernie at develer dot com>
- To: gcc at gcc dot gnu dot org
- Date: Sun, 3 Aug 2003 08:38:21 +0200
- Subject: cross-compiling libiberty in gcc-3.4
- Organization: Develer S.r.l.
Hello,
I'm struggling trying to build the 3.4 snapshot of 20030730 on m68k-elf.
libiberty fails to build for the target when compiling
libiberty/strerror.c. The immediate cause is that sys_errlist
is non-const in libiberty and const in the C library headers
(I'm using uClibc).
The funny thing is that gcc 3.3 does not bother building strerror()
because m68k-elf/libiberty/config.h defines HAVE_SYS_ERRLIST.
For some reason, the test for sys_errlist fails in 3.4 only for
the target build of libiberty. This is config.h:
/* Define if you have the sys_errlist variable. */
/* #undef HAVE_SYS_ERRLIST */
/* Define if you have the sys_nerr variable. */
/* #undef HAVE_SYS_NERR */
I've investigated the failure in m68k-elf/libiberty/config.log,
but it seems no test have ever been run for these.
Comparing all of libiberty from 3.3.1 with 3.4 revealed no
suspicious changes...
So, where does autoconf get this result from?
--
// Bernardo Innocenti - Develer S.r.l., R&D dept.
\X/ http://www.develer.com/
Please don't send Word attachments - http://www.gnu.org/philosophy/no-word-attachments.html