Thanks. I’m just trying to hack around the error: > Undefined symbols for architecture x86_64
Another possible solution is: > add -stdlib=libstdc++ to the linking command See: https://stackoverflow.com/questions/19637164/c-linking-error-after-upgrading-to-mac-os-x-10-9-xcode-5-0-1 I’ll try both, and go with the least-yuck one that works. What’s the Portfile directive to add -stdlib=libstdc++ to the linker? > On Nov 21, 2019, at 19:46, Joshua Root <[email protected]> wrote: > > On 2019-11-22 09:35 , Steven Smith wrote: >> >> CC=/usr/bin/clang++ >> >> >> Error on the Mac: Undefined symbols for architecture x86_64 · Issue #285 · >> nlohmann/json >> https://github.com/nlohmann/json/issues/285#issuecomment-348090484 > > Is the build system really using $CC to compile C++ code? The usual > convention is that CC is the C compiler and CXX is the C++ compiler. > Naturally using the wrong one will cause problems. > > Sticking to the convention is greatly preferable, but if for some reason > you really need to name a C++ compiler in CC, this will do it: > > # Yuck > configure.cc ${configure.cxx} > > - Josh
smime.p7s
Description: S/MIME cryptographic signature
