<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Wed, Oct 28, 2015 at 9:28 PM, Jeffrey Walton <span dir="ltr"><<a href="mailto:noloader@gmail.com" target="_blank">noloader@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div id=":2ny" class="a3s" style="overflow:hidden">So I'm clear: MacPorts does not test compiling under the compiler it<br>
provides? Is that correct?</div></blockquote></div><br>MacPorts only uses those compilers when clang will not work. It uses the system compiler whenever possible, to avoid possible compatibility issues. In general, the gcc* compilers are provided for users to use and/or for those (few) ports that won't work with the Xcode-provided clang.<br><br>I have this feeling you were expecting something like a Linux distribution, a full ecosystem that is regression tested with itself.</div><div class="gmail_extra">MacPorts is a BSD ports-like system intended to make available things that are not provided with OS X, on a best effort basis.</div><div class="gmail_extra"><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>