Subject: Re: gnu/usr.bin/gcc/libgcc: __word__ unknown
To: der Mouse <mouse@Collatz.McRCIM.McGill.EDU>
From: Jason Thorpe <thorpej@nas.nasa.gov>
List: port-sparc
Date: 02/23/1996 10:51:21
On Fri, 23 Feb 1996 10:28:58 -0500
der Mouse <mouse@Collatz.McRCIM.McGill.EDU> wrote:
> ===> gnu/usr.bin/gcc/libgcc
> cc -O -I/sources/working-usr-src/gnu/usr.bin/gcc/libgcc/../common -I/sources/working-usr-src/gnu/usr.bin/gcc/libgcc/../arch -I/sources/working-usr-src/gnu/usr.bin/gcc/libgcc/../arch/sparc -Werror -c -DL__gcc_bcmp -o __gcc_bcmp.o /sources/working-usr-
src/gnu/usr.bin/gcc/libgcc/libgcc2.c
> /sources/working-usr-src/gnu/usr.bin/gcc/libgcc/libgcc2.c:82: unknown machine mode `__word__'
>
> This looks to me like a chicken-and-egg problem, trouble building the
> new gcc with the old (this is the first build I've done since the sparc
> port was switched to the new gcc). Is it possible to get around it by
> building and installing some parts and then building the rest, the way
> the last error like this worked?
This has been on current-users before, but to recap:
cd /usr/src/gnu/usr.bin/gcc
make
<pukes in libgcc>
(cd cc; make install)
(cd cc1; make install)
(cd cc1plus; make isntall)
(cd g++; make install)
cd libgcc; make; make install
cd ../
make
That ought to pretty much do it.
--------------------------------------------------------------------------
Jason R. Thorpe thorpej@nas.nasa.gov
NASA Ames Research Center Home: 408.866.1912
NAS: M/S 258-6 Work: 415.604.0935
Moffett Field, CA 94035 Pager: 415.428.6939