On Fri, Oct 5, 2012 at 12:13 PM, Andrew Pinski <pins...@gmail.com> wrote: > On Fri, Oct 5, 2012 at 7:32 AM, Pavel Chupin <pavel.v.chu...@gmail.com> wrote: >> I can't configure libstdc++ separately. To reproduce: >> >> mkdir BUILD >> cd BUILD >> ../libstdc++-v3/configure >> >> Error: >> make: *** No rule to make target >> `/users/pvchupin/android/toolchain/gcc/gcc-4.8/BUILD/../libgcc/gthr-default.h', >> needed by `bits/gthr-default.h'. Stop. >> >> See fix attached. >> >> Ok for trunk and 4.7? > > Why do you want to compile libstdc++ separately from GCC? I think you > need to explain why you want to do that. In fact libstdc++ depends on > libgcc internals is not a bug but rather a feature.
One more thing is that for cases where target==host!=build, you can just use the libraries which are produced by the cross compiler and use "make all-host" and "make install-host" for the programs. This should simplify how Yocto builds the "native" GCC and not worrying about building libstdc++ separately. Thanks, Andrew Pinski > > Thanks, > Andrew Pinski > > > >> >> 2012-10-05 Pavel Chupin <pavel.v.chu...@intel.com> >> >> Fix missing gthr-default.h issue on separate libstdc++ configure >> * libstdc++-v3/acinclude.m4: Define glibcxx_thread_h. >> * libstdc++-v3/include/Makefile.am: Use glibcxx_thread_h. >> * libstdc++-v3/Makefile.in: Regenerate. >> * libstdc++-v3/configure: Regenerate. >> * libstdc++-v3/doc/Makefile.in: Regenerate. >> * libstdc++-v3/include/Makefile.in: Regenerate. >> * libstdc++-v3/libsupc++/Makefile.in: Regenerate. >> * libstdc++-v3/po/Makefile.in: Regenerate. >> * libstdc++-v3/python/Makefile.in: Regenerate. >> * libstdc++-v3/src/Makefile.in: Regenerate. >> * libstdc++-v3/src/c++11/Makefile.in: Regenerate. >> * libstdc++-v3/src/c++98/Makefile.in: Regenerate. >> * libstdc++-v3/testsuite/Makefile.in: Regenerate. >> >> -- >> Pavel Chupin >> Intel Corporation