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 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
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 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
> On 20 Feb 2018, at 8:00 pm, macports-users-requ...@lists.macports.org wrote:
>
>> This happens recurrently to me, usually after significant updates.
>>
>> The last time was some months ago, so I forget exactly what I did, but it
>> involved the location of xauth and the ssh config on the ta
