-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Joanne Pham wrote: > How to check the compiler options in this case?
You can use 'nm' to see which symbols are present so that will help track functions that have been included or excluded from which you can deduce some flags. gcc does embed some information to help. Use objdump -s -j SECTION dllname. Example $ objdump -s -j .comment sqlite.so Contents of section .comment: 0000 00474343 3a202855 62756e74 7520342e .GCC: (Ubuntu 4. 0010 332e332d 35756275 6e747534 2920342e 3.3-5ubuntu4) 4. 0020 332e3300 00474343 3a202855 62756e74 3.3..GCC: (Ubunt [.. it goes on like this ..] At least I can identify which compiler was used. However the actual compiler flags (eg -O, -DXXX) are not recorded by default in object files or libraries. If you require SQLite to be compiled a particular way then use the amalgamation. Roger -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAknvovQACgkQmOOfHg372QSupACeMt1xw74Jcs1u2UctKTRybvs+ aOAAnR+YN1QgjJWLFfeKCfA/KU2C6d/H =sw5y -----END PGP SIGNATURE----- _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
