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?)
> The current workaround I now use is to symlink all those checked
>headers: 'stdlib.h', 'unistd.h', 'string.h' and 'limits.h' into
>'$prefix/$target/sys-include' from '$prefix/$target/include', so
>that they will not be replaced with stubs during the GCC-build.
Thanx for the tip! Now I can build a complete toolchain
(binutils-2.13, newlib-1.11.0) for --target=m68k-elf using *either*
gcc-3.3, or gcc-3.2.3.
--
Peter Barada
peter@baradas.org