On Fri, Aug 26, 2016 at 12:09 PM, Ken Cunningham < [email protected]> wrote:
> There must be a more elegant answer / way to do this, though. And there > must be some explanation for what happens to cause this -- but I don't know > what it is at present. Possibly some port somewhere along the line is buggy and not using the libcxx settings; when you reset everything you remove that port, and everything is fine until it gets pulled back in and then subsequent builds find it. (If this is happening in clang itself, it could be a build tool that is not compatible.) -- brandon s allbery kf8nh sine nomine associates [email protected] [email protected] unix, openafs, kerberos, infrastructure, xmonad http://sinenomine.net
_______________________________________________ macports-users mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-users
