This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: failure building gcc-3.3 (broken libiberty/vsprintf.c or build?)
- From: Peter Barada <peter at baradas dot org>
- To: kai dot ruottu at luukku dot com
- Cc: gcc at gcc dot gnu dot org, crossgcc at sources dot redhat dot com
- Date: Tue, 20 May 2003 23:45:51 -0400 (EDT)
- Subject: Re: failure building gcc-3.3 (broken libiberty/vsprintf.c or build?)
- References: <20030520053204.ADDB298982@baradas.org> <3EC9F529.6060106@luukku.com>
> Ok, you have added all kind of 'nice-looking' options into your
>configure-command, but the important '--with-newlib' is missing...
>If it is missing, the already installed '$prefix/$target/lib' stuff
>will be checked for the existing C functions. This option simply tells
>that newlib will be used as the chosen C library.
>
> So my thought is that all your problems come from leaving the
>'--with-newlib' away. Sometimes the so-called 'fixed' newlib headers,
>found before the original newlib headers when compiling 'libiberty',
>can cause problems too. So you should check your $build/gcc/include
>too for the 'fixes' done if using newlib.
Wow, learn something new every day. After chanig my config to be:
/home/peter/work/cvs-local/xgcc/gcc-3.3/configure \
--with-gcc-version-trigger=/home/peter/work/cvs-local/xgcc/gcc-3.3/gcc/version.c \
--host=i686-pc-linux-gnu --target=m68k-elf --prefix=/tmp/m68k-elf \
--with-newlib --enable-languages=c,c++ \
--with-local-prefix=/tmp/m68k-elf/m68k-elf --norecursion
it builds for me.
What's weird is that gcc-3.2.3 built fine with that configure. Now
I'm going back and seeing if this configure works for gcc-3.2.3.
Thanx for the pointers...
--
Peter Barada
peter@baradas.org