It's going to be something like that. I've also seen a few executables at times that are linked to both -libc++ and to -libstdc++, and you just know that can't be a good thing. (Probably exactly what you're suggesting.)
No doubt, although this libc++ upgrade enables quite a bit more software to build and run, you do need to keep your wits about you. K On 2016-08-26, at 9:13 AM, Brandon Allbery wrote: > > On Fri, Aug 26, 2016 at 12:09 PM, Ken Cunningham > <ken.cunningham.web...@gmail.com> 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 > allber...@gmail.com ballb...@sinenomine.net > unix, openafs, kerberos, infrastructure, xmonad http://sinenomine.net
_______________________________________________ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
