<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Honestly, I’m in the same situation as you are. I just started working on libc++ and I’m trying to figure out what configurations are supported — it’s not obvious to me at all. Marshall, Eric or other long date contributors may know better — I’m not the best resource. For now I’m focused on getting LLVM 7 out the door, but in the future I would like to document a matrix of supported configurations:<div class=""><br class=""></div><div class="">Linux:</div><div class=""><div class=""><font face="Menlo" class="">libc++ | ABI library | Unwind library </font></div><div class=""><font face="Menlo" class="">--------------------------------------------</font></div><div class=""><font face="Menlo" class="">LLVM 6 | libc++abi LLVM 6 | libunwind LLVM 6</font></div><div class=""><font face="Menlo" class="">LLVM 6 | libsupc++ vX.Y | libunwind LLVM 6</font></div><div class=""><font face="Menlo" class="">LLVM 7 | libc++abi LLVM 7 | libunwind LLVM 7</font></div><div class=""><font face="Menlo" class="">LLVM 7 | libsupc++ vX.Y | libunwind LLVM 7</font></div><div class=""><font face="Menlo" class="">trunk | trunk | trunk</font></div><div class=""><br class=""></div><div class="">etc...</div><div class=""><br class=""></div><div class="">And we should have something similar for Darwin, where we also need to be compatible with older system libraries:</div><div class=""><br class=""></div><div class=""><font face="Menlo" class="">libc++ | ABI library | Unwind library </font></div><div class=""><font face="Menlo" class="">-----------------------------------------------</font></div><div class=""><font face="Menlo" class="">LLVM 6 | libc++abi LLVM 6 | libunwind LLVM 6</font></div><div class=""><font face="Menlo" class="">LLVM 6 | libc++abi macOS X.Y | libunwind macOS X.Y</font></div><div class=""><font face="Menlo" class="">LLVM 7 | libc++abi LLVM 7 | libunwind LLVM 7</font></div><div class=""><font face="Menlo" class="">LLVM 7 | libc++abi macOS X.Y | libunwind macOS X.Y</font></div><div class=""><font face="Menlo" class="">trunk | trunk | trunk</font></div><div class=""><br class=""></div><div class="">This would be a large matrix, but that's okay. And then we can have one tester per supported configuration and we can stop having surprises during releases. Also, if a user comes with an unsupported configuration, the answer would be easy.</div></div><div class=""><br class=""></div><div class="">Like I said, there might be a good answer to your question and I just don’t know it — but in all cases it does not seem to be documented officially.</div><div class=""><br class=""></div><div class="">Louis</div><div class=""><div class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Aug 30, 2018, at 11:43, Andrew Brownsword <<a href="mailto:andrew.e.brownsword@gmail.com" class="">andrew.e.brownsword@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">It would be most helpful if the was a known good combination of libraries and settings that would net a working toolchain for ARM7hf Ubuntu 16.04, with CLang 7 and libc++. I’ve been trying libc++abi and libunwind mostly (and compiler-rt in the last day or two) as I had build problems with the various gcc-based paths. What is the recommended path to follow though? A lot of options are provided but clearly it’s a minefield of broken paths.<br class=""><br class=""><blockquote type="cite" class="">On Aug 30, 2018, at 7:04 AM, Louis Dionne <<a href="mailto:ldionne@apple.com" class="">ldionne@apple.com</a>> wrote:<br class=""><br class="">Are you building your test program with -fno-rtti? I’ve seen a problem where if libc++ is built with RTTI and exceptions enabled, and a program is built with exceptions enabled BUT -fno-rtti, exceptions thrown from the program will not be caught.<br class=""><br class="">Louis<br class=""><br class=""><blockquote type="cite" class="">On Aug 25, 2018, at 15:20, Andrew Brownsword via cfe-dev <<a href="mailto:cfe-dev@lists.llvm.org" class="">cfe-dev@lists.llvm.org</a>> wrote:<br class=""><br class="">I have built the llvm/clang 7.0.0 rc2, including libc++/libc++abi/libunwind for my Ubuntu 16.04 Linux 32-bit ARM7 hf target. A trivial c++17 test program with just this try/catch block:<br class=""><br class="">try { auto result = stoul(“foo”); } catch (...) { std::cerr << “caught!” << std::endl; }<br class=""><br class="">fails to print “caught!” Instead it just aborts. If no exceptions are thrown, programs built with this toolchain behave as expected.<br class=""><br class="">I have tried numerous variations of the toolchain, compile and link steps (including alternatives to the cxxabi), however they all run into various errors or ultimately give the same runtime abort.<br class=""><br class="">Any suggestions for how to get a functioning Linux armhf clang/libc++ 7.0.0 toolchain?<br class=""><br class="">_______________________________________________<br class="">cfe-dev mailing list<br class=""><a href="mailto:cfe-dev@lists.llvm.org" class="">cfe-dev@lists.llvm.org</a><br class="">http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev<br class=""></blockquote><br class=""></blockquote></div></div></blockquote></div><br class=""></div></div></body></html>