Kai I started fresh but now I am hitting the below error . My assessment of the problem is why this problem is coming because I compiled/configured my binutils also with same sysroot . /local/gagupta/gccfolder/crosstoolsv1/x86_64-redhat-linux-gnu/bin/ld: skipping incompatible /local/gagupta/gccfolder/crosstoolsv1/sysroot/usr/lib/libc.so when searching for -lc /local/gagupta/gccfolder/crosstoolsv1/x86_64-redhat-linux-gnu/bin/ld: cannot find -lc I have set every single thing LDFLAGS , CPATH , C_INCLUDE_PATH , CPLUS_INCLUDE_PATH , SYSROOT = $PREFIX/sysroot but nothing Thanks Gaurav -----Original Message----- From: Kai Ruottu [mailto:kai.ruottu@xxxxxxxxxxx] Sent: Thursday, March 07, 2013 3:20 PM To: GUPTA, GAURAV G (GAURAV) Cc: gcc-help@xxxxxxxxxxx Subject: Re: issues with gcc 4.4.6 7.3.2013 5:14, GUPTA, GAURAV G (GAURAV) kirjoitti: > 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 I don't fully understand what your last option is for (http://gcc.gnu.org/install/configure.html), but my guess is that one wants to build a custom native GCC which doesn't use the usual '/usr/include'. Do you know why you are using this? If you are creating a cross GCC then this may cause troubles. A cross GCC should automatically search the '$sysroot/usr/include', nothing else than the '--with-sysroot=$sysroot' is required. > I am still getting these error .I have extracted stdc++ rpm in my sysroot. What you did? The stdc++ headers and libraries will be created and installed during the GCC build and install. So there shouldn't be any C++ headers and libraries for the target when starting, only the C ones which usually means (all or some) the 'glibc-*.rpm's and the 'kernel-headers-*.rpm' being extracted into the sysroot. In your case the should be both the default 64-bit and the optional 32-bit glibc binaries extracted so the sysroot has both the lib & lib64 and usr/lib & usr/lib64 binaries and the one usr/include. > /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 > It looks like the process stopped in the libstdc++-v3 install phase... Was the directory '$BUILD/x86_64-redhat-linux-gnu/libstdc++-v3' (where $BUILD is your GCC build dir) even created and filled during the build? What about the '$BUILD/x86_64-redhat-linux-gnu/32/libstdc++-v3' for the 32-bit libstdc++-v3? Maybe you should start with a clean board what comes to the sysroot and leave the ' --with-native-system-header-dir=${CLFS}/usr' away from the GCC configure, and start with bare sources after a 'make distclean' or simply doing a 'rm -f -r' in the GCC build directory...
