<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="">while tracking down an openmp issue in ImageMagick that appears to have been due to fopenmp flags in libraw <<a href="https://trac.macports.org/ticket/59610" class="">https://trac.macports.org/ticket/59610</a>> , we stumbled across the fact that libraw had a hard link to libstdc++ in it’s pkgconfig files. I removed that while doing other things, thinking it was just bitrot from the last decade, as the proper c++ standard library is selected by the cxx compiler.<div class=""><br class=""></div><div class="">But the libraw dev says that even when building C code, libraw indeed needs to link against a c++ standard library for a few functions <<a href="https://github.com/LibRaw/LibRaw/issues/248" class="">https://github.com/LibRaw/LibRaw/issues/248</a>> so that’s why it has the hardcoded link.</div><div class=""><br class=""></div><div class="">So that will not automatically be done by clang when building C code, of course.</div><div class=""><br class=""></div><div class="">To my moderate surprise, I see Catalina still has /usr/lib/libstdc++.dylib</div><div class=""><br class=""></div><div class="">So the question:</div><div class=""><br class=""></div><div class="">reinstate libraw’s hard link against libstdc++.dylib and move on, OR set the pkgconfig files to link against the configure.cxx_stdlib at the time libraw is being installed (and hope that works out for whatever is building something that is using the libraw pkgconfig files).</div><div class=""><br class=""></div><div class="">Or some better idea?</div><div class=""><br class=""></div><div class="">thx.</div><div class=""><br class=""></div><div class="">Ken</div><div class=""><br class=""></div></body></html>