This is the mail archive of the crossgcc@sources.redhat.com mailing list for the crossgcc project.
See the CrossGCC FAQ for lots more information.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
-> I must have missed something. Why do you need to build glibc first? I guess I should have asked for help in getting the "Build final gcc" phase of crosstool.sh to complete when the "Build glibc and linuxthreads" phase fails. Something seems to be happening during the process of building GLIBC that is required to make the final GCC. I ran demo-7450.sh which builds successfully through "Build gcc-core" but fails when attempting to build GLIBC. Then, I deleted the lines in crosstool.sh which build GLIBC, added the "--nounpack" option to demo-7450.sh, and ran that. This is where I got the previously mentioned errors: In file included from /usr/local/src/crosstool-0.28-rc35/build/powerpc-7450-linux-gnu/gcc-3.4.1-glibc-2.1.3/gcc-3.4.1/gcc/crtstuff.c:62: /usr/local/src/crosstool-0.28-rc35/build/powerpc-7450-linux-gnu/gcc-3.4.1-glibc-2.1.3/gcc-3.4.1/gcc/tsystem.h:85:19: errno.h: No such file or directory By examining the log of a successful build, I noticed "errno.h" was installed by "make -C stdlib subdir_install" within the GLIBC directory. However, this requires some other targets to be built first, which also have prerequisites, and so on). Perhaps there is a way to use the headers which were installed in order to build bootstrap compiler? -- Tom ------ Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/ Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |