issues with gcc 4.4.6

[GUPTA, GAURAV G (GAURAV)]

Dear Kai 

This is my configure options 


AR=ar LDFLAGS="-Wl,-rpath,/local/gagupta/gccfolder" \
        ${SOURCES_GCC}/configure \
        --prefix=${CLFS_CROSS_TOOLS} --target=${CLFS_TARGET} --disable-decimal-float --with-sysroot=${CLFS} --with-native-system-header-dir=${CLFS}/usr --enable-languages=c,c++,objc,obj-c++ --enable-shared --disable-nls --disable-libgomp --enable-__cxa_atexit --enable-long-long --disable-libmudflap --enable-threads=posix --enable-checking=release --enable-c99


make[2]: Leaving directory `/local/gagupta/gccfolder/crosscompile/gcc-build/libiberty'

I am still getting these error .I have extracted stdc++ rpm in my sysroot.


/bin/sh: line 3: cd: x86_64-redhat-linux-gnu/libstdc++-v3: No such file or directory
make[1]: *** [install-target-libstdc++-v3] Error 1
make[1]: Leaving directory `/local/gagupta/gccfolder/crosscompile/gcc-build'
make: *** [install] Error 2
pwd
[1]+  Exit 2            


-----Original Message-----
From: Kai Ruottu [mailto:kai.ruottu@wippies.com] 
Sent: Wednesday, March 06, 2013 4:25 PM
To: GUPTA, GAURAV G (GAURAV)
Cc: gcc-help@gcc.gnu.org
Subject: Re: issues with gcc 4.4.6

6.3.2013 11:50, GUPTA, GAURAV G (GAURAV) kirjoitti:

> I had a very basic question - Do I need to build the GCC in 2 stages or 3 stages. Please note that mine is the case of cross compilation .Because as I understood it in first stage gcc needs to be built without any headers  .

Some bullshit in the net has caused this misunderstanding?

A normal cross GCC for a system target like Linux is a "second 
incarnation of the original native GCC".
So one needs to do only :

1. copy the target C library into the $sysroot

2. configure and build the target binutils, hosted on the $host system, 
using '--with-sysroot=' to point
    to the target C library

3. configure and build the target GCC, hosted on the $host system, using 
'--with-sysroot=' to point
    to the target C library

and be happy!

A normal cross GCC so could for instance be one hosted on a Fedora 
14/i386 system and targeted to a
Fedora 18/ARM system, and use the glibc RPMS for the latter system as 
the target C library in the
chosen $sysroot...