<p><span class="h-card" translate="no"><a href="https://mastodon.social/@mcc" class="u-url mention">@<span>mcc</span></a></span> llvm libunwind is essentially an internal component of the platform runtime. it is documented in the Itanium (EH)ABI.</p><p>the other libunwind you&#39;re dealing with is some other thing with the same name that&#39;s unrelated except for its purpose</p><p>libgcc_s and llvm libunwind implement the same interface and are mutually exclusive; the other libunwind could be used together with each</p><p>does this clarify</p>

<p>Now I get to uninstall the libc from my computer completely and replace it with a different one. Because it&#39;s the only remaining way to fix this linker error.</p>

<p>I lose <a href="https://mastodon.social/@mcc/113807871925781727" target="_blank" rel="nofollow noopener" translate="no"><span class="invisible">https://</span><span class="ellipsis">mastodon.social/@mcc/113807871</span><span class="invisible">925781727</span></a></p><p>This is the limit of my ability to debug. I cannot work out why an undocumented function, whose name begins with an underscore, from library A is not being provided by a library B which has no documentation at all, when building someone else&#39;s code that I do not know the purpose of. I lose! I thought I could just keep powering through build errors but now.</p>

<p><span class="h-card" translate="no"><a href="https://chaos.social/@ReneRebe" class="u-url mention">@<span>ReneRebe</span></a></span> <span class="h-card" translate="no"><a href="https://chaos.social/@esden" class="u-url mention">@<span>esden</span></a></span> <span class="h-card" translate="no"><a href="https://social.1bitsquared.com/@1bitsquared" class="u-url mention">@<span>1bitsquared</span></a></span> yeah, we should be getting that out of SFDP...</p>

<p>Update: Building Rust on a local computer against llvm libunwind I get these linker errors which makes me think maybe it&#39;s not api compatible</p>

<p>Googling about the hp libunwind, it sounds like it&#39;s a series of unw_ functions. Which sounds like the GCC libunwind interface. But that is vibes; if someone *believes* the two are API incompatible, *what could I tell them to convince them otherwise*?</p><p>Also, is it weird that llvm libunwind seems to literally has no usage documentation at all? Did I miss something? Is Google simply cooked?</p>

<p>Say I&#39;m talking to someone who believes the clang libunwind and gcc libunwind are API incompatible.</p><p>I&#39;m fairly certain this is incorrect. But I can&#39;t *prove* it.</p><p>The GCC libunwind docs are here. It lists all these unw_ functions. <a href="https://www.nongnu.org/libunwind/docs.html" target="_blank" rel="nofollow noopener" translate="no"><span class="invisible">https://www.</span><span class="">nongnu.org/libunwind/docs.html</span><span class="invisible"></span></a></p><p>The clang libunwind docs are here <a href="https://bcain-llvm.readthedocs.io/projects/libunwind/en/latest/" target="_blank" rel="nofollow noopener" translate="no"><span class="invisible">https://</span><span class="ellipsis">bcain-llvm.readthedocs.io/proj</span><span class="invisible">ects/libunwind/en/latest/</span></a> and they are… build instructions. Nothing else. It describes itself as implementing &quot;the HP libunwind interface&quot;. Google doesn&#39;t find such a thing and I don&#39;t think HP-UX is supported.</p>

<p>Providence Public Library has a special collection on printing and typefaces, and recently hosted this exhibit on our history of letterpress printing (going back to Ben Franklin&#39;s brother, who fled religious bigots in Boston for RI). Check out these lovely custom curtains!</p>

i have a new composition