This is the mail archive of the crossgcc@sourceware.org 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 have seen some problem in glibc getting strange unwinding code in past if you remove the glibc header stepi was just perusing the cross-LFS docs and noticed that *their* recipe for building a toolchain didn't involve the installation of glibc headers between the binutils and bootstrap gcc steps.
the comments in crosstool.sh for that step seem to imply that it's not really clear if that step is required, so i did a quick test. i configured my mini-ct script to build for powerpc and commented out the entire glibc headers step.
i also then commented out the two commands in the bootstrap gcc step:
# cp ${GLIBC_HEADERS_DIR}/bits/stdio_lim.h ${HEADERS_DIR}/bits # touch ${HEADERS_DIR}/gnu/stubs.h
and invoked my script, which i set up to run only up to and including the bootstrap gcc phase. it ran to completion, no problems so, at least for powerpc, the glibc headers step is *not* necessary to build the bootstrap compiler.
just to play it safe, i tried this again for the sh3 architecture.
that didn't work so well. i'll report on that shortly after i make
sure it's not something stupid i did.
rday
------ Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/ Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com
------ 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] |