<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Mon, Jun 22, 2015 at 1:17 PM, levi silvers <span dir="ltr"><<a href="mailto:silversster@gmail.com" target="_blank">silversster@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 style="word-wrap:break-word"><div><div style="margin:0px;font-size:13px;font-family:Menlo">The following ports are currently installed:</div><div style="margin:0px;font-size:13px;font-family:Menlo"> gcc47 @4.7.4_3</div><div style="margin:0px;font-size:13px;font-family:Menlo"> gcc47 @4.7.4_5 (active)</div><div style="margin:0px;font-size:13px;font-family:Menlo"> gcc49 @4.9.2_1</div><div style="margin:0px;font-size:13px;font-family:Menlo"> gcc49 @4.9.2_2 (active)</div><div style="margin:0px;font-size:13px;font-family:Menlo"> gcc_select @0.1_8 (active)</div><div><span style="font-family:Menlo;font-size:13px"><br></span></div></div><div><span style="font-family:Menlo;font-size:13px">Is it normal to have two versions of gcc active? I suspect this is causing a problem with a program which depends on gcc. </span></div></div></blockquote><div><br></div><div>Entirely normal. Note that they are not available as "gcc" by default; instead there will be e.g. /opt/local/bin/gcc-mp-4.7.</div><div><br></div><div>"gcc" will by default be /usr/bin/gcc which, depending on what version of Xcode or Command Line Tools is present, is either an ancient llvm-gcc-4.2 or a wrapper for Clang. Also note that most ports will default to using Xcode's clang directly on a recent (10.8 and up, and at least some 10.7 depending on Xcode version) system.</div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><div><span style="font-family:Menlo;font-size:13px">Can I specify which version I would like macports to use? </span></div></div></blockquote><div><br></div><div>Specify configure.compiler=something (e.g. configure.compiler=macports-gcc-4.7), but using this is a bad idea unless you are specifically trying to diagnose a problem; in this case you should report a bug against the port at <a href="https://trac.macports.org">https://trac.macports.org</a>. </div></div><br clear="all"><div>What port is causing problems, and can you provide a full build log (that is, after running "port clean" on the port in question so that no leftovers from a previous build are around)?</div><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>