Kai I think I have been able to build the GCC 4.4.6 with custom sysroot . This is what I did 1 .Extracted Glibc*( utils , common for i686 and x86_64 rpm ) 2. Extracted Linux headers into sysroot 3. Extracted Glibcheaders into sysroot . After this is it necessary to do configure GCC 3 times and build Thanks Gaurav -----Original Message----- From: Kai Ruottu [mailto:kai.ruottu@xxxxxxxxxxx] Sent: Sunday, March 17, 2013 2:03 PM To: GUPTA, GAURAV G (GAURAV) Cc: gcc-help@xxxxxxxxxxx Subject: Re: issues with gcc 4.4.6 On 17.3.2013 5:23, GUPTA, GAURAV G (GAURAV) wrote: > > 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 You need both the default 64-bit and the optional 32-bit C library in sysroot, the 64-bit libraries in 'lib64' & 'usr/lib64' and the 32-bit libraries in 'lib' & 'usr/lib'. You maybe installed only the 32-bit ones? But the 'libc.so' normally isn't a binary file but a text file, a linker script, which puts the linker to link against the 'libc.so.6' and 'libc_nonshared.a' and maybe 'ld-linux.so.2' (in the 32-bit case). So complaining about the script is a little odd. Please check the situation in the '*lib64' and '*lib' directories. If you don't need the 32-bit anywhere, the use '--disable-multilib' in the GCC configure, then the build doesn't try to create the 32-bit 'libgcc', 'libstdc++' etc.
