Recompiling the toolchain with -gnu suffix does not help. I get the same error.
2010/8/11 Sergey Naumov <[email protected]> > I have attached output of gcc. > type -p ./powerpc-unknown-linux-gcc returns nothing. > > It seems that gcc passes crti.o (and another crt*.o files) to ld without > directory prefix. > When I copied *crt*.o files from /tools/lib to /cross-tools/bin and > compiled my test helloworld.c application in this directory, all was OK. > > Thanks for quick reply. > > 2010/8/11 Joe Ciccone <[email protected]> > >> On 08/11/2010 06:32 AM, Sergey Naumov wrote: >> >> some significant update: /cross-tools/powerpc-unknown-linux-gcc >> -print-search-path gives a list of search directories for libraries and >> /opt/builder/tools/lib is there. (my /opt/builder is your ${CLFS}). So ld >> should find /opt/builder/tools/lib/crti.o, but it does not! >> >> I have used eglibc-2.11.2 instead of 2.12 because there was compile >> errors there (multiple #defines due to multiple inclusion of some .def >> file), other packages have the same versions as in instruction. >> >> >> ---------- Forwarded message ---------- >> From: Sergey Naumov <[email protected]> >> Date: 2010/8/11 >> Subject: GCC stage2(final) for powerpc fails >> To: [email protected] >> >> >> Hello. >> >> I have tried to build toolchain for powerpc according with your >> instructions (http://cross-lfs.org/view/svn/ppc/), >> but for gcc-final I have encountered a linker error: "crti.o - no such >> file or directory". >> I found crti.o in /tools/lib, but linker can't see it. Could you help with >> this issue? >> >> Thanks in advance, >> Sergey Naumov. >> >> Could you please provide the output of these commands? >> >> type -p powerpc-unknown-linux-gcc >> echo 'int main() {}' | powerpc-unknown-linux-gcc -x c - -v -Wl,--verbose >> >> Also, please restart your build with -gnu on the end of your target >> triplet. The -gnu on the end specifies that you are using a GNU libc. I >> don't know what it is with people wanting to leave that off lately. I think >> I should clarify something too. CLFS_TARGET will not affect the target >> triplet of the final system, it only affects /tools. Which you will delete >> when you are done anyway. The final system is automatically detected with >> config.guess. >> >> -- >> >> Joe Ciccone >> >> >> _______________________________________________ >> Clfs-dev mailing list >> >> [email protected] >> http://lists.cross-lfs.org/listinfo.cgi/clfs-dev-cross-lfs.org >> >> >
_______________________________________________ Clfs-dev mailing list [email protected] http://lists.cross-lfs.org/listinfo.cgi/clfs-dev-cross-lfs.org
