On Feb 20, 2018, at 08:34, Joshua Kordani wrote:
> Not the OP, but regarding DYLD_LIBRARY_PATH, I don't understand how to make
> use of dylib's provided by macports in my own programs without setting this
> flag. I've read in several places that, esp with macports, this should not
> be necess
Hi,
- On 20 Feb, 2018, at 15:34, Joshua Kordani jkord...@lsa2.com wrote:
> Not the OP, but regarding DYLD_LIBRARY_PATH, I don't understand how to
> make use of dylib's provided by macports in my own programs without
> setting this flag. I've read in several places that, esp with macports,
>
> On Feb 20, 2018, at 06:34, Joshua Kordani wrote:
>
> Not the OP, but regarding DYLD_LIBRARY_PATH, I don't understand how to make
> use of dylib's provided by macports in my own programs without setting this
> flag. I've read in several places that, esp with macports, this should not
> be
Not the OP, but regarding DYLD_LIBRARY_PATH, I don't understand how to
make use of dylib's provided by macports in my own programs without
setting this flag. I've read in several places that, esp with macports,
this should not be necessary, but I don't know what the *right way* is.
On 2/19/1
On Feb 19, 2018, at 13:37, Qianqian Fang wrote:
> I don't know what was changed recently, the built-in git command from Xcode
> stopped working with the following error
>
> fangq@jinwy:~/space/git/Project/autobuild/mcx$ git pull
> dyld: lazy symbol binding failed: Symbol not found: _iconv_open
