<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Wed, Dec 17, 2014 at 9:47 AM, Joshua Root <span dir="ltr"><<a href="mailto:jmr@macports.org" target="_blank">jmr@macports.org</a>></span> wrote:<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">Xcode 3.x is not the right version to use with Lion, 4.x is. 3.1 is for<br>
Leopard and 3.2 is for Snow Leopard. IIRC, 3.2.6 didn't even work right<br>
on Lion, so I wouldn't expect it to work on Mavericks.<br></blockquote><div><br></div><div>Sorry, typo, 4.6.3 is the exact Lion SDK version that was installed. My mistake. :)</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>The Apple-endorsed way to build for an older OS version has always been<br>
to use the latest Xcode and set MACOSX_DEPLOYMENT_TARGET to the oldest<br>
version you want to target.<br></blockquote><div><br></div><div>Yes, this is the approach I am using.</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
MacPorts doesn't officially support doing this, mainly because autoconf and similar systems consider it to be cross-compiling and need you to<br>
tell them about the target manually, instead of being able to detect the characteristics of the build machine automatically.</blockquote><div><br></div><div>Gotcha.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
> Ideally, I'd like to have two MacPorts installs that I can build software<br>
> against... One for Mavericks and a second instance for Lion.<br>
<br>
You can certainly configure MacPorts to use a different prefix when<br>
building it from source.<br></blockquote><div><br></div><div> Ok, so this option is only available when building the MacPorts software from source. I'd rather not add more cruft. I'll fire up a Lion VM for this, thank you.</div></div></div></div>