2010/10/1 Khem Raj <[email protected]>: > On Fri, Oct 1, 2010 at 3:09 AM, Thilo Fromm <[email protected]> wrote:
>> >> I tracked it down - libunwind publishes unwind.h, and gcc uses an internal >> file of the same name while being built. > > Yes gcc has its own version of libunwind which it used unless > configured with --with-system-libunwind > IIUC the problem happens with target gcc not with cross-gcc. target > gcc is built using cross-gcc and > <sysroot>/use/include could be preferred over the location of > libunwind.h which is in gcc sources > If thats the case then we need to fix gcc build to not look into > standard sysroot/usr/include but prefer > the local unwind.h when its using internal libunwind. The problem > would not show up if the libunwind versions > were matching but that may not be the case always and I dont know of > hand how we can fix the gcc configury/build > to ignore installed unwind.h > > You workaround would only work if build sequence was followed if some > one just cleaned gcc and rebuild it > the problem will resurface. > Thanks for the analysis Khem. This is indeed more or less what I had expected. For me this patch gets a NAK as it does only masks the problvem in some cases but not really solves it. Frans. _______________________________________________ Openembedded-devel mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
