Re: projects/clang380-import for TARGET_ARCH=powerpc64: /lib/libgcc_s.so.1 is incompatible with using the pair: /usr/lib/libc++.so.1 and /lib/libcxxrt.so.1 for C++ exception handling

[In part: My references to libc++ should have been to libcxxrt. Also: devel/powerpc64-gcc produced the incomplete .eh_frame information.] On 2016-Feb-24, at 5:07 PM, Mark Millard wrote: > > [Deliberate top posting an history removal for significant new information.] > >

Re: projects/clang380-import for TARGET_ARCH=powerpc64: /lib/libgcc_s.so.1 is incompatible with using the pair: /usr/lib/libc++.so.1 and /lib/libcxxrt.so.1 for C++ exception handling

[Deliberate top posting an history removal for significant new information.] I've finally traced the low level details of the powerpc64 _Unwind_RaiseException stuck looping failure. What I've submitted into the defect is basically that for clang 3.8.0's .eh_frame information generation in

projects/clang380-import for TARGET_ARCH=powerpc64: /lib/libgcc_s.so.1 is incompatible with using the pair: /usr/lib/libc++.so.1 and /lib/libcxxrt.so.1 for C++ exception handling

For TARGET_ARCH=powerpc64 it looks like FreeBSD's /lib/libgcc_s.so.1 is incompatible with using the pair: /usr/lib/libc++.so.1 and /lib/libcxxrt.so.1 . Evidence details follow. (Now using projects/clang380-import -r295902 as a context.) src.conf was set up to have things such that the