On Tue, Mar 1, 2016 at 10:35 AM, Mojca Miklavec <mo...@macports.org> wrote:
> The question is: should I bother upstream (wxWidgets) with trying to > circumvent the problem? It probably makes no sense to report the > compiler problem to anyone (clang/apple developers) as it is most > likely fixed already (clang-3.4 works just fine). > > In the package I can simply blacklist the broken compiler. > I'd just blacklist the compiler. I doubt the Wx folks are any more interested in compiler archaeology than Apple is. -- brandon s allbery kf8nh sine nomine associates allber...@gmail.com ballb...@sinenomine.net unix, openafs, kerberos, infrastructure, xmonad http://sinenomine.net
_______________________________________________ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
