>I solved that problem already via merging both Solaris and ksh93 libcmd, >see >http://polaris.blastwave.org/browser/on/branches/ksh93/gisburn/prototype002/m1_ast_ast_imported/us r/src/lib/libcmd/ >- it seems to work perfectly and the risk of a namespace clash is IMO >tiny since all the new symbols start with "b_" (and libcmd is a private >library anyway so we (or better: Sun) control all consumers (and can fix >them on demand) ... :-) ).
Ok; what's the cost for linking with this additional stuff (startup cost, extra memory used, particularly unshared data/bss? It's used by most if not all daemon processes (I count 32 processes using it on my system alone). Have you created .spec files for the ksh libraries? What other tools use these libraries? (If it's only ksh, I am of the opinion that they need to be statically linked to ksh and not shipped as libraries; if they're used bby many other tools then, of course, not) We don't want to get into some "Mozilla" DLL craze. (If it isn't shared, it shouldn't be a shared library; and if it is shared, it shouldn't be 40 libraries) Casper
