Installing GCC-3.2 problem.
ca9mbu at isis.sunderland.ac.uk
Mon Sep 9 12:22:28 PDT 2002
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.
>>> > I completed all previous steps without any problems.
>>> Therefore try the following
>>> mv /static/lib/gcc-lib/i686-pc-linux-gnu/3.2/include/stdio.h
>> And that is by the way, the same error I've got when tried to run
>> make CC="gcc -I/usr/include" bootstrap
>> (trying to fix previous case)
> OK. It has got all bitter and twisted. So
> mv /static/lib/gcc-lib/i686-pc-linux-gnu/3.2/include
> mv /static/lib/gcc-lib/i686-pc-linux-gnu/3.2/include.bak
> mkdir /static/lib/gcc-lib/i686-pc-linux-gnu/3.2/include
> That gets rid of all those headers generated from your base
> Delete your gcc-3.2 and gcc-build directories, Sorry.
> Unpack clean source and try again.
Thanks for your attempts at trying to fix this for us (yes I'm using
Knoppix-3.1 as well and suffering the same problem).
I renamed the include directory to include.bak as sugessted but then
./configure exits with a failure:
checking for inline... (cached) inline
checking for volatile... yes
checking for long double... yes
checking for long long int... yes
checking for __int64... no
checking for built-in _Bool... yes
checking size of short... configure: error: cannot determine a size for
Configure in /usr/src/tarballs/gcc-build/gcc failed, exiting.
After a bit of trial and error I did:
...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.
Hope this helps,
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