<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div class=""><div class="">We find it builds fine with an Xcode clang > 1001. It does not build with the latest Xcode clang available on 10.13, but it does build with clang-9.0 on 10.13 (just confirmed it with your build line).</div><div class=""><br class=""></div><div class="">Here's a log from 10.13 successfully building libc++abi.dyib (and the rest of clang) using clang-9 last night.</div><div class=""><br class=""></div><div class=""><<a href="https://build.macports.org/builders/ports-10.13_x86_64-builder/builds/85088/steps/install-port/logs/stdio" class="">https://build.macports.org/builders/ports-10.13_x86_64-builder/builds/85088/steps/install-port/logs/stdio</a>>.</div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">hope this helps,</div><div class=""><br class=""></div><div class="">K</div></div><div class=""><br class=""></div><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Jun 2, 2020, at 6:42 AM, Louis Dionne via libcxx-dev <<a href="mailto:libcxx-dev@lists.llvm.org" class="">libcxx-dev@lists.llvm.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html; charset=us-ascii" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Hmm, something like a year old clang should work, so this must be an actual bug. Can you provide a link to a gist containing the full output of the build command? Also, please use `-v` so we can see individual compiler invocations.<div class=""><br class=""></div><div class="">Thanks,</div><div class="">Louis<br class=""><div class=""><br class=""><blockquote type="cite" class=""><div class="">On Jun 2, 2020, at 04:50, <a href="mailto:llvm@dyatkovskiy.com" class="">llvm@dyatkovskiy.com</a> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">Nope, it fails for TOT as well.</div><div class=""> </div><div class=""><div class="">commit e70cf280f80c0933dd500ff18c7a17af8057b28c (HEAD -> master, origin/master, origin/HEAD)</div><div class="">Author: Sam Parker <<a href="mailto:sam.parker@arm.com" class="">sam.parker@arm.com</a>></div><div class="">Date: Tue Jun 2 09:04:20 2020 +0100</div><div class=""> </div><div class="">[NFC][ARM][AArch64] Test runs</div><div class=""> </div><div class="">Add code size tests runs for memory ops for both architectures.</div><div class=""> </div><div class="">Error message:</div><div class=""><div class=""> </div><div class="">Undefined symbols for architecture x86_64:</div><div class="">"__ZTIDu", referenced from:</div><div class="">-exported_symbol[s_list] command line option</div><div class="">"__ZTIPDu", referenced from:</div><div class="">-exported_symbol[s_list] command line option</div><div class="">"__ZTIPKDu", referenced from:</div><div class="">-exported_symbol[s_list] command line option</div><div class="">"__ZTSDu", referenced from:</div><div class="">-exported_symbol[s_list] command line option</div><div class="">"__ZTSPDu", referenced from:</div><div class="">-exported_symbol[s_list] command line option</div><div class="">"__ZTSPKDu", referenced from:</div><div class="">-exported_symbol[s_list] command line option</div><div class="">ld: symbol(s) not found for architecture x86_64</div></div></div><div class=""> </div><div class="">Thanks!</div><div class="">Stepan</div><div class=""> </div><div class="">02.06.2020, 02:50, "via libcxx-dev" <<a href="mailto:libcxx-dev@lists.llvm.org" class="">libcxx-dev@lists.llvm.org</a>>:</div><blockquote class="">I'm sorry, I reproduced this issue only with clang version which is 4 weeks old. Commit ff4a3ee4.<div class="">It wasn't yet tested with newer clang versions. I'll check tomorrow and let you know.<div class=""> </div><div class="">Thanks!</div><div class="">Stepan<br class=""> <div class="">02.06.2020, 01:12, "via libcxx-dev" <<a href="mailto:libcxx-dev@lists.llvm.org" class="">libcxx-dev@lists.llvm.org</a>>:</div><blockquote class=""><div class=""><div class="">Louis,</div><div class="">how recent clang should be? I have this error for 31th of May version, for this commit 595212569.</div><div class=""> </div><div class="">Thanks!</div><div class=""> </div><div class="">01.06.2020, 23:54, "Louis Dionne" <<a href="mailto:ldionne@apple.com" class="">ldionne@apple.com</a>>:</div><blockquote class=""><div style="word-wrap:break-word" class="">Hi,<div class=""> </div><div class="">I just updated <a href="http://llvm.org/PR43749" class="">http://llvm.org/PR43749</a>, which I wasn't aware of. As I explain in the bug report:</div><div class=""> </div><div class=""><div class=""> The issue is that the compiler emits type information for fundamental types in libc++abi, and your compiler doesn't know about char8_t yet, so it doesn't emit the type information for those. libc++abi tries to export these symbols and it fails to do so, because they haven't been generated in the dylib by the compiler.</div><div class=""> </div><div class=""> Getting a linker error is quite nice, because otherwise you'd be producing a libc++abi.dylib that doesn't work properly at runtime (say if you try to use typeid(char8_t) in your program).</div><div class=""> </div><div class="">I hope that answers your question. The problem should go away if you use a recent Clang. If it doesn't please ping me again.</div><div class=""> </div><div class="">Thanks,</div><div class="">Louis</div><div class=""> <blockquote class=""><div class="">On Jun 1, 2020, at 15:39, <a href="mailto:llvm@dyatkovskiy.com" class="">llvm@dyatkovskiy.com</a> wrote:</div> <div class=""><div class="">Hi Louis!</div><div class=""> </div><div class="">I found your commit in llvm-project, libcxxabi, namely this one:</div><div class=""><div class=""> </div><div class="">commit 223df5b54021cfa4c67d4e09e1dc1b3b9e6a9de7 (refs/bisect/bad)</div><div class="">Author: Louis Dionne <<a href="mailto:ldionne@apple.com" class="">ldionne@apple.com</a>></div><div class="">Date: Thu Jun 27 20:17:22 2019 +0000</div><div class=""> </div><div class="">In this commit you added exported symbols for different platforms for libcxxabi, for apple:</div><div class=""> </div><div class="">I'm currently trying to build it for Mac OS 10.13.6, x86_64, and bumped into unresolved symbols errors:</div><div class=""> </div><div class=""><div class=""><div class="">Undefined symbols for architecture x86_64:</div><div class="">"__ZTIDu", referenced from:</div><div class="">-exported_symbol[s_list] command line option</div><div class="">"__ZTIPDu", referenced from:</div><div class="">-exported_symbol[s_list] command line option</div></div></div><div class=""> </div><div class="">I noticed that you added itanium-base.exp for APPLE platforms by default (no other conditions):</div><div class=""> </div><div class="">> if (APPLE)</div><div class=""><div class="">> target_link_libraries(cxxabi_shared PRIVATE "-Wl,-exported_symbols_list,${CMAKE_CURRENT_SOURCE_DIR}/../lib/itanium-base.exp")</div><div class=""> </div><div class="">I'm not expert of x86_64 arch, especially for darwin. Are we using Itanium ABI by default on Mac OS 10.13 for x86_64 arch?</div><div class="">If so, what did I miss, for there are symbols which must be exported, but absent in my compilation. I compile libcxxabi with following commands:</div><div class=""> </div><div class="">cmake -G "Ninja" -DCMAKE_BUILD_TYPE=Release -DCMAKE_INSTALL_PREFIX=$BUILD_DIR/install -DLLVM_ENABLE_PROJECTS="libcxx;libcxxabi" $SRC_DIR</div><div class="">ninja -j8</div><div class=""> </div><div class="">There is also bug, which seems to be related to this commit:</div><div class=""><a href="https://bugs.llvm.org/show_bug.cgi?id=43749" class="">https://bugs.llvm.org/show_bug.cgi?id=43749</a></div><div class=""> </div><div class="">Thanks!</div><div class="">Stepan Dyatkovskiy</div><div class=""> </div></div></div></div></blockquote></div></div></div></blockquote></div><div class=""><p class="">_______________________________________________<br class="">libcxx-dev mailing list<br class=""><a href="mailto:libcxx-dev@lists.llvm.org" class="">libcxx-dev@lists.llvm.org</a><br class=""><a href="https://lists.llvm.org/cgi-bin/mailman/listinfo/libcxx-dev" class="">https://lists.llvm.org/cgi-bin/mailman/listinfo/libcxx-dev</a></p></div></blockquote><div class=""> </div><div class=""> </div><div class=""> </div><div class=""> </div></div></div>,<p class="">_______________________________________________<br class="">libcxx-dev mailing list<br class=""><a href="mailto:libcxx-dev@lists.llvm.org" class="">libcxx-dev@lists.llvm.org</a><br class=""><a href="https://lists.llvm.org/cgi-bin/mailman/listinfo/libcxx-dev" class="">https://lists.llvm.org/cgi-bin/mailman/listinfo/libcxx-dev</a></p></blockquote></div></blockquote></div><br class=""></div></div>_______________________________________________<br class="">libcxx-dev mailing list<br class=""><a href="mailto:libcxx-dev@lists.llvm.org" class="">libcxx-dev@lists.llvm.org</a><br class="">https://lists.llvm.org/cgi-bin/mailman/listinfo/libcxx-dev<br class=""></div></blockquote></div><br class=""></body></html>