-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Turns out those libraries are available in my instantclient folder, which is aliased correctly (DYLD_LIBRARY_PATH).
Emmanuel Bourgerie Web developer Dublin, Ireland (+353) 8 144 5278 http://bourgerie.fr/ Confus avec "BEGIN PGP SIGNED MESSAGE" ? http://weusepgp.info/fr Confused with "BEGIN PGP SIGNED MESSAGE"? http://weusepgp.info/ On 13/11/2013 14:41, Emmanuel Bourgerie wrote: > So, > > $ otool -L /usr/lib/libclntsh.dylib.11.1 > /usr/lib/libclntsh.dylib.11.1: > /ade/b/2649109290/oracle/rdbms/lib/libclntsh.dylib.11.1 > (compatibility version 0.0.0, current version 0.0.0) > /ade/b/2649109290/oracle/ldap/lib/libnnz11.dylib (compatibility > version 0.0.0, current version 0.0.0) /usr/lib/libSystem.B.dylib > (compatibility version 1.0.0, current version 159.1.0) > > If I understand correctly, I miss those /ade/* libs, right? > > Emmanuel Bourgerie Web developer Dublin, Ireland (+353) 8 144 5278 > http://bourgerie.fr/ > > Confus avec "BEGIN PGP SIGNED MESSAGE" ? http://weusepgp.info/fr > Confused with "BEGIN PGP SIGNED MESSAGE"? http://weusepgp.info/ > > On 09/11/2013 10:58, Till Oliver Knoll wrote: >> Am 08.11.2013 um 23:03 schrieb Thiago Macieira >> <thiago.macie...@intel.com <mailto:thiago.macie...@intel.com>>: > >>> On sexta-feira, 8 de novembro de 2013 21:44:23, Emmanuel >>> Bourgerie wrote: >>>> They are fine AFAIK. Is there a command to double-check? >>> >>> "otool" should be able to print the headers, but the "file" >>> command should be enough. If file says that it's a Mach-O fat >>> binary, check which architectures are contained inside. > >> file and otool do the job just fine. Another one would be lipo. > >> I found a nice summary of those tools and their usage here: > >> http://wiki.herzbube.ch/index.php/Mac_OS_X_Programming > >> However IIRC if an architecture mismatch between your binary and >> the library you are trying to link against was really the case >> then the linker would actually give a hint like "architecture x64 >> not found in binary" or "architecture x64 not supported" instead >> of an ordinary "library not found" (I think that was the actual >> problem of the OP, right?) > >> Anyway, the above mentioned tools should quickly help tracking >> down the issue. > >> Cheers, Oliver > > >> _______________________________________________ Interest mailing >> list Interest@qt-project.org >> http://lists.qt-project.org/mailman/listinfo/interest > > _______________________________________________ Interest mailing > list Interest@qt-project.org > http://lists.qt-project.org/mailman/listinfo/interest > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.14 (Darwin) iQEcBAEBAgAGBQJSg5JXAAoJEKKGwafy1e1+VGQIAKkXAYe4el/qqshuxlbicI90 tzr3R7Rx37Do0fE8NXWbl8z9Na07OOVLKqF/964lnPPgoB6Mxwe9iZKtwqs21w0M tEG/8L0UjfD2u3XK5n5k3mYmcRw8bST3Y2NDsC5Fv2+qjfjrMcHJcAxLIbqqa8nY bQMk5muhiHUP4VawJcHfrZ3y2L5ojho2N+so2iC2i+NSw2UkjGj1gppkE5mvJZkq ARpCJLBzQarutawuZjr+LXLCA5UymxcvLRz2bp2iSvqNzuWYg1HCdrNyZlda4Xki G59yK9Pihk8uUtR8fHhnA2ZWwDe3f95gvPERUQpO1dCZxM6TbOJaCA0m2WBdSDg= =6QRW -----END PGP SIGNATURE----- _______________________________________________ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
