>Actually, looking at the code, I don't see how /usr/ucblib is used by >4.x *binaries*. I.e. if you have a SunOS 4.x binary, it looks like you >get the libraries in /usr/4lib, using the a.out exec module. I don't >think you wind up using any of the ELF stuff in /usr/ucblib.
dump -Lv /usr/4lib/sbcp **** DYNAMIC SECTION INFORMATION **** .dynamic: [INDEX] Tag Value [1] NEEDED libmapmalloc.so.1 [2] NEEDED libc.so.1.9 [3] NEEDED libucb.so.1 [4] NEEDED libnsl.so.1 [5] NEEDED libc.so.1 [6] RUNPATH /usr/4lib:/usr/ucblib [7] RPATH /usr/4lib:/usr/ucblib (sbcp is for "Static Binary Compatibility"; however, it's easy to have a partially statically linked executable so I think sbcp is always loaded for an a.out executable) Also, /usr/4lib/libc.so.1.9 is linked to libucb.so.1. >So, maybe I didn't name this inappropriately after all. > >What *would* break, are 4.x *sources* that have been *compiled* on SunOS >5.x. And 4.x binary compatibility :-) Casper
