On 10/29/10 08:17 AM, Piotr Jasiukajtis wrote:
Build 134:ldd libapr-0.so.0.9.17 libsendfile.so.1 => /lib/libsendfile.so.1 librt.so.1 => /lib/librt.so.1 libm.so.2 => /lib/libm.so.2 libsocket.so.1 => /lib/libsocket.so.1 libnsl.so.1 => /lib/libnsl.so.1 libresolv.so.2 => /lib/libresolv.so.2 libpthread.so.1 => /lib/libpthread.so.1 libc.so.1 => /lib/libc.so.1 libmp.so.2 => /lib/libmp.so.2 libmd.so.1 => /lib/libmd.so.1 libscf.so.1 => /lib/libscf.so.1 libuutil.so.1 => /lib/libuutil.so.1 libgen.so.1 => /lib/libgen.so.1 libsmbios.so.1 => /usr/lib/libsmbios.so.1 Build 135: ldd libapr-0.so.0.9.17 ./libapr-0.so.0.9.17: unknown capability: 0 libsendfile.so.1 => /lib/libsendfile.so.1 librt.so.1 => /lib/librt.so.1 libm.so.2 => /lib/libm.so.2 libsocket.so.1 => /lib/libsocket.so.1 libnsl.so.1 => /lib/libnsl.so.1 libresolv.so.2 => /lib/libresolv.so.2 libpthread.so.1 => /lib/libpthread.so.1 libc.so.1 => /lib/libc.so.1 libmp.so.2 => /lib/libmp.so.2 libmd.so.1 => /lib/libmd.so.1 libscf.so.1 => /lib/libscf.so.1 libuutil.so.1 => /lib/libuutil.so.1 libgen.so.1 => /lib/libgen.so.1 libsmbios.so.1 => /usr/lib/libsmbios.so.1 I think the original build environment for this library was Solaris 10.
Ok, but this isn't telling us how the object was built. We've been building a lot of objects on 135 and above, and I've not seen this issue before :-) Are you building your objects with gcc, studio, ld(1)? Are you post-processing the objects someway after they have been built? Seeing the link-line that creates libapr-0.so.0.9.17, and any post-post processing carried out on this file might shed some light, but I suspect we'd have to re-create the build of this object to get to the bottom of the "corruption". BTW, the bad capability diagnostic fix has been integrated for build 153. 6990845 unknown capabilities tags are poorly diagnosed -- Rod. _______________________________________________ tools-linking mailing list [email protected]
