On Thu, Dec 29, 2011 at 3:26 PM, Bruce Johnson
<john...@pharmacy.arizona.edu> wrote:
>> Does the output of:
>>
>> otool -L
>> /Library/Perl/5.12/darwin-thread-multi-2level/auto/DBD/mysql/mysql.bundle
>>
>> list your custom MySQL libraries anywhere? If the linker can't find
>> your MySQL libraries, then you'll need to give the linker some hints.
>> You can set the environment variable DYLD_LIBRARY_PATH to point to the
>> path where your custom libraries are located, and things should then
>> work.
>
> Not sure:
>
> bruces-Mac-Pro:lib johnson$ otool -L
> /Library/Perl/5.12/darwin-thread-multi-2level/auto/DBD/mysql/mysql.bundle
> /Library/Perl/5.12/darwin-thread-multi-2level/auto/DBD/mysql/mysql.bundle:
> libmysqlclient.18.dylib (compatibility version 18.0.0, current version
> 18.0.0)
> /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current
> version 159.1.0)
>
> it lists the dylib, but not the path. Should it show the path?
I would say yes, here's mine (from MacPorts):
otool -L
/opt/local/lib/perl5/vendor_perl/5.14.2/darwin-thread-multi-2level/auto/DBD/mysql/mysql.bundle
/opt/local/lib/perl5/vendor_perl/5.14.2/darwin-thread-multi-2level/auto/DBD/mysql/mysql.bundle:
/opt/local/lib/mysql5/mysql/libmysqlclient.16.dylib (compatibility
version 17.0.0, current version 17.0.0)
/opt/local/lib/libz.1.dylib (compatibility version 1.0.0, current
version 1.2.5)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current
version 125.2.11)
/opt/local/lib/libssl.1.0.0.dylib (compatibility version 1.0.0,
current version 1.0.0)
/opt/local/lib/libcrypto.1.0.0.dylib (compatibility version 1.0.0,
current version 1.0.0)
> (and also, this is not a 'custom' MySQL library, I installed this version of
> MySQL:
>
> "Mac OS X ver. 10.6 (x86, 64-bit), DMG Archive" from here:
>
> http://dev.mysql.com/downloads/mysql/
>
> I'd hope that the standard installer would work out of the box with the DBD
> module..)
Apple does bundle MySQL as part of OS X Server... this is what I would
call "the standard install of MySQL on OS X", since you would file
bugs with Apple instead of Oracle when something in MySQL-related
doesn't work. It's a semantic difference, but when you're looking for
support because of an issue, it's kind of important.
Since you're not using the version of MySQL that was bundled with the
operating system, *you* will need to fiddle with the bits to get
everything to work correctly.
Did you try setting the DYLD_LIBRARY_PATH environment variable prior
to running otool/your Perl script?
Thanks,
Brian
