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 have not tried the approach of running libc's make install-headers before building GCC. You surely need to do "make install-headers no_deps=t"; I'm not confident that will really work either, but it's worth a try. What I have done is to build GCC first with no headers installed (using --enable-languages=c), use make -k and ignore errors building libgcc, install gcc. Then build libc and install it (libs and headers, programs won't link). Then go back and do a complete GCC build and install. Then go back and finish building libc. It would be good to get a coherent procedure for building a gcc+libc cross environment from scratch specified somewhere and make sure it works. ------ 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] |