<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Oct 29, 2015 at 9:15 PM, David Strubbe <span dir="ltr"><<a href="mailto:dstrubbe@macports.org" target="_blank">dstrubbe@macports.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">The problem that was being mentioned here is that gcc48 doesn't build. That should not imply that ports already built with gcc48 have any problem. So there is no need to recompile anything. Just when building new ports use a different version not gcc48.</blockquote></div><br>But there are ports (and I believe one of them was at the start of this thread) that bake specific compilers into themselves, and therefore have compiler-specific variants.</div><div class="gmail_extra"><br></div><div class="gmail_extra">That said, the fix for this is to look for any +gcc48 on ports to be installed and replace it with +gcc49. (Ports that had +gcc48 as default variant *should* use a different compiler already; if not, file a bug.)<br clear="all"><div><br></div>-- <br><div class="gmail_signature"><div dir="ltr"><div>brandon s allbery kf8nh sine nomine associates</div><div><a href="mailto:allbery.b@gmail.com" target="_blank">allbery.b@gmail.com</a> <a href="mailto:ballbery@sinenomine.net" target="_blank">ballbery@sinenomine.net</a></div><div>unix, openafs, kerberos, infrastructure, xmonad <a href="http://sinenomine.net" target="_blank">http://sinenomine.net</a></div></div></div>
</div></div>