> - libcxxabi is probably the new way to go instead of libcxxrt; last > time I checked there was a chicken and egg problem: libcxxabi needed > clang + libc++ to build, so bootstrapping the stack was a bit > painful.
I give libcxxabi a try. Does anybody has a bit insight in the current status of the llvm's bundled libunwind in libcxxabi, i.e. is it trivially portable? If yes, this might clean up the dependency chain quite a bit. Best, Matthias
