Installing GCC-3.2 problem.

Chris Lingard chris at stockwith.co.uk
Mon Sep 9 13:38:41 PDT 2002


Matthew Burgess wrote:

> Chris Lingard wrote:
> 
>> Goldman Michael wrote:
>> 
>>> 
>>> 
>>>> Goldman Michael wrote:
>>>>
>>>> >
>>>> > Book version : cvs 20020907
>>>> > Chapter 6 : Installing GCC-3.2
>>>> > Mother system is KNOPPIX Linux on CD (Based on Debian) with
>>>> > gcc 2.95.4, glibc-2.2.5, kernel-2.4.19-xfs.
>>>> >

> 
> After a bit of trial and error I did:
> 
> mv /static/lib/gcc-lib/i686-pc-linux-gnu/3.2/include
> /static/lib/gcc-lib/i686-pc-linux-gnu/3.2/include.bak
> mv /static/lib/gcc-lib/i686-pc-linux-gnu/3.2/include.bak/*.h
> /static/lib/gcc-lib/i686-pc-linux-gnu/3.2/include/
> rm /static/lib/gcc-lib/i686-pc-linux-gnu/3.2/include/stdio.h
> 
> ...rest of commands to compile gcc-3.2 from CVS book
> 
> This allows the compile to complete successfully, and the new gcc
> compiles a helloworld type c++ program correctly.
> 
> If there's anything in those instructions that's glaringly wrong
> (i.e. I may be contaminating my LFS system with bad headers, etc)
> then please let me know, but at least I've got a working gcc.
> 

No, you should be fine now.  You have built glibc against kernel
headers, and now you have built gcc against that.  You will be
deleting /static when you have finished; your new gcc will have
"fixed" the headers from your new glibc.

This is an unavoidable problem;  the chapter 5 gcc is building
against whatever distro you use; so will put things in
/static/lib/gcc-lib/....../include.  These may not be compatible
with your new system.

GNU used to quote $5000 dollars to port their systems to a new
machine.  You have just done it for free.

Chris




-- 
Unsubscribe: send email to listar at linuxfromscratch.org
and put 'unsubscribe lfs-dev' in the subject header of the message



More information about the lfs-dev mailing list