If someone could give me some clues about how to debug this it would be
great.
I'm trying to figure out why "it" fails to load a particular dylib under
macOS.
"it" meaning that I'm not sure who is actually failing, but I suspect it is
actually a failure detected and reported by dlopen(3) itself,
Am 20.09.2016 um 15:32 schrieb Luís Oliveira :
>
> On Tue, Sep 20, 2016 at 10:53 AM, Jim Newton wrote:
>> CL-USER> (cffi::list-foreign-libraries)
>> (...
>> #> :LIBCAIRO #P"/usr/local/Cellar/cairo/1.12.16_1/lib/libcairo.dylib"
>>
On Tue, Sep 20, 2016 at 10:53 AM, Jim Newton wrote:
> CL-USER> (cffi::list-foreign-libraries)
> (...
> #:LIBCAIRO #P"/usr/local/Cellar/cairo/1.12.16_1/lib/libcairo.dylib"
> (truename=#P"/usr/local/Cellar/cairo/1.12.16_1/lib/libcairo.2.dylib")>)
> CL-USER>
>
> However,
Hi Frank, thanks for the information. If you always use /usr/local/lib
then what do you do when you need to run two different independent
applications which have different requirements?
On Tue, Sep 20, 2016 at 3:44 PM, Frank Goenninger wrote:
> Am 20.09.2016 um 15:32 schrieb Luís
Jim,
loading a specific version of a shared library requires two things:
a. Use absolute path to the library in the cffi lib spec
b. Make sure the dependencies (see output of otool -L ) (the paths to the
dependencies) are at the beginning of the paths set in the environment variable