<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">I'll echo Seablade's experience on Macports. "they be dragons there…" I almost had to re-install my mac to fix the cruft that was left over after a complete macports un-install. not a lot of fun.<div><br></div><div>-Ben</div><div><br><div><div>On Apr 7, 2013, at 9:43 PM, Thomas Vecchione <<a href="mailto:seablaede@gmail.com">seablaede@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Sat, Apr 6, 2013 at 4:02 PM, Elie Richa <span dir="ltr"><<a href="mailto:eliericha@gmail.com" target="_blank">eliericha@gmail.com</a>></span> wrote:<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr"><div class="gmail_extra">Since I started using MacPorts I gave it a dedicated prefix, so in theory I should be able to remove its interference by removing it from environment variables (or am I too optimist? ;). I'll try that and see if it helps.</div>
<br></div></blockquote><div><br></div><div>Theory and reality tend to break down when talking about Macports interference in this process. IIRC Paul(?) and I both tried different solutions for this many years back and completely gave up essentially, the best option is just not to involve macports at all.<br>
<br></div><div> Seablade <br></div></div></div></div>
_______________________________________________<br>ardour-dev mailing list<br><a href="mailto:ardour-dev@lists.ardour.org">ardour-dev@lists.ardour.org</a><br>http://lists.ardour.org/listinfo.cgi/ardour-dev-ardour.org<br></blockquote></div><br></div></body></html>