I'd like to know if my direction is ok. I can look into other issues releated to this and fix them, but it doesn't make much sense if separate build is not supported and can be easily broken in the future. This patch is enough for 4.7 to have build working (at least in Android environment).
Is it ok for release it into trunk and 4.7? I'll take care of remaining trunk issues with other patches if necessary. 2012/10/9 Benjamin De Kosnik <b...@redhat.com>: > >> On Android NDK libstdc++ is configured, built and packaged separately. >> The problem is not dependency on libgcc sources but rather dependency >> on the symlink which is generated during libgcc build and cannot be >> found if libstdc++ is configured and built separately. >> It was working fine for 4.4 and 4.6. This issue has been introduced >> in 4.7. > > I can verify that building this way works for 4.6. > > This style of build, building separately, has not been known to work > before. In fact, it was explicitly broken for years. I am quite > surprised (but delighted) to see it working in 4.6. > > Separate builds not mentioned here: > http://gcc.gnu.org/onlinedocs/libstdc++/manual/configure.html > > This patch is fine. Alone, it's not enough to get you were you want to > go, as the build then dies in AC_OUTPUT, and libtool is not generated. > > > -benjamin -- Pavel Chupin Software Engineer Intel Corporation