<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Thu, Oct 1, 2015 at 4:16 AM, Jan Stary <span dir="ltr"><<a href="mailto:hans@stare.cz" target="_blank">hans@stare.cz</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On Sep 30 16:09:13, <a href="mailto:stephen.butler@gmail.com">stephen.butler@gmail.com</a> wrote:<br>
> I'm transitioning from Fink to MacPorts. When I initially setup my MacPorts<br>
> install I *thought* I had removed all my Fink stuff from my path.<br>
<br>
</span>How exactly did you remove all your Fink stuff?<br>
Be removing it "from your path", do you mean that you left it<br>
installed in /sw, just removed /sw from your PATH?<br>
<span class=""></span></blockquote><div><br></div><div>I had removed the ". /sw/bin/init.sh" from my .profile and restarted my Terminal sessions. At least... I thought I had restarted them all...</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">
> Everything was working and I was happy, so I deleted my /sw directory.<br>
> But now I see that the MacPorts build system has picked up /sw/bin/gnutar<br>
> (among, possibly, other things I haven't discovered).<br>
<br>
</span>This means that you have *not* removed /sw before building MacPorts.</blockquote><div><br></div><div>Yeah :( I think maybe I didn't expect a source build of MacPorts to capture stuff from /sw, but it obviously did. I later scanned my /opt/local/{bin,lib} with find+otool looking for linkage against /sw and didn't find any. But then I found it baked into a couple python modules (distutils and numpy). So just to be sure I rebuilt all my ports after I had rm -fr /sw.</div></div></div></div>