Subject: Re: libgcc won't build (960210)
To: None <mouse@Collatz.McRCIM.McGill.EDU>
From: Greg Earle <earle@isolar.Tujunga.CA.US>
List: current-users
Date: 02/26/1996 21:58:56
>> Trying to build everything, I get this:
>> 
>> cc -O -I/mnt/src/gnu/usr.bin/gcc/libgcc/../common -I/mnt/src/gnu/usr.bin/gcc/libgcc/../arch  -I/mnt/src/gnu/usr.bin/gcc/libgcc/../arch/i386  -c -DL__gcc_bcmp -o __gcc_bcmp.o /mnt/src/gnu/usr.bin/gcc/libgcc/libgcc2.c
>> /mnt/src/gnu/usr.bin/gcc/libgcc/libgcc2.c:76: no data type for mode `XF'
>> /mnt/src/gnu/usr.bin/gcc/libgcc/libgcc2.c:82: unknown machine mode `__word__'
>> *** Error code 1
>> 
>> I'm using the 960210 sources, but getting the most recent gcc source
>> from the tree didn't help a bit.  What am I doing wrong?
> 
> You're building new gcc with old, probably.
> 
> When I ran into this on the SPARC (the first time I did a build after
> the switch to the new gcc), I posted to port-sparc, where a helpful
> soul said to do a "make install" in gnu/usr.bin/gcc and then pick up
> where it left off.  I did this; the make install installed in about six
> subdirectories and then crashed because libgcc hadn't been built, but
> it had installed enough pieces for the build of libgcc to complete ok.

So what is one supposed to do if one doesn't want to install a new gcc?

If you use $DESTDIR, "make install" in gnu/usr.bin/gcc will put the new bits
in $DESTDIR/usr/bin and they won't get used at all.

(Having just been bitten by this myself, this is frustrating.)

	- Greg