The issue you describe is an issue with the *deployment* of clang in MacPorts/OSX. Something else.
... or an issue with the package itself that prevents it being compiled with clang (I have come across plenty of issues myself of code that compiles with gcc but fails with clang, because of bugs in the code itself that gcc lets through... and vice versa, both compilers have their personal nuances). Or perhaps an issue with way the port is set up.
_______________________________________________ macports-users mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-users
