On Tue, 12 Oct 1999, Mike Crowe wrote:
> Benjamin Stocks wrote:
> > make[3]: Entering directory
> > `/usr/local/arm/src/gcc-2.95/arm-linux/libiberty'
> > make[3]: *** No targets. Stop.
> > make[3]: Leaving directory
> > `/usr/local/arm/src/gcc-2.95/arm-linux/libiberty'
> > make[2]: *** [../libiberty/libiberty.a] Error 2
> > make[2]: Leaving directory
> > `/usr/local/arm/src/gcc-2.95/arm-linux/libstdc++'
> > make[1]: *** [all-target-libstdc++] Error 2
> > make[1]: Leaving directory `/usr/local/arm/src/gcc-2.95'
> > make: *** [cross] Error 2
Normally, this is caused by trying to make gcc in the gcc subdirectory rather
than in the top gcc-2.95* top directory.
What follows is extracted from a long mail with subject:"Re: Toolchain guide"
in the Mail Archive. It has never been confirmed by Philip Blundell or Chris
Rutter but, Hey! it worked for me ;-)
>One would have to build gcc 3 timesin order to have a completely fonctionnal
>toolchain (built form scratch):
>-Build/install binutils
>-Patch/Build/install gcc
>-Build/install gcc again
>-Build/install glibc
>-Build/install gcc a third time without the -Dinhibit_libc corrections.
Hope it will help,
--
Fran�ois Desloges
[EMAIL PROTECTED]
unsubscribe: body of `unsubscribe linux-arm' to [EMAIL PROTECTED]
