<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Mon, Dec 9, 2013 at 7:43 AM, Brian D. McGrew <span dir="ltr"><<a href="mailto:brian@visionpro.com" target="_blank">brian@visionpro.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5"><span style="color:rgb(34,34,34)">Ah, right, thanks for the clarification. We set DYLD_FALLBACK_LIBRARY_PATH, not the other. But, I don't set that in a new terminal. I have to run a script that sets up my build environment, which is 'usually' the first thing I do. So popping a new terminal and running port without my build environment works fine. But, if I set my env and DYLD_FALLBACK… is set, it no workee… very slow, don't know why. but the fix, I just won't have DYLD_ set when I run port. Still, never seen this before and if anyone knows why it's happening, I'd be interested in knowing.</span></div>
</div></blockquote><div> </div></div>We can't tell for certain without knowing what your environment looks like, but it is very likely that your replacement libraries are shadowing some standard function in a way that breaks MacPorts (and may affect other OS X native software although perhaps not as drastically). There are some debugging DYLD_ variables you can set to show what is getting bound from where, but without knowing what's in the libraries you have been forcing it to use we can't even guess.<br clear="all">
<div><br></div>-- <br><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>