Joerg Schilling wrote:
> > This may be preferred if we want to change the filesystem layout of the
> > ksh93 distribution and move stuff like "libast" (same was done with
> > openssl&co.) to on/usr/src/lib/ (see
> > http://cvs.opensolaris.org/source/xref/on/usr/src/lib/). AFAIK in that
> > case we have to create own own Makfiles.
>
> How many of the AT&T sources do you like to integrate into OpenSolaris?
Just those from ast-ksh.2005-02-02.tar.bz2
> Do you like to add everything?
Heh. No - but take a look at the "ldd" output below, please:
% ldd /lib/libshell.so.1
linux-gate.so.1 => (0xffffe000)
libast.so.5 => /lib/libast.so.5 (0x40079000)
libcmd.so.1 => /lib/libcmd.so.1 (0x4014f000)
libdll.so.1 => /lib/libdll.so.1 (0x40180000)
libc.so.6 => /lib/tls/libc.so.6 (0x401a2000)
/lib/ld-linux.so.2 (0x80000000)
... libshell.so needs libast, libcmd and libdll (which are all part of
ast-ksh.2005-02-02.tar.bz2).
My question is whether these libraries should be treated as
ksh93-private, libshell.so-private or standalone APIs (being some kind
of semi-private API for official Solaris releases (AFAIK the manual
pages describe such a state as "evolving")) ... the last option may be
my preference...
----
Bye,
Roland
--
__ . . __
(o.\ \/ /.o) roland.mainz at nrubsig.org
\__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer
/O /==\ O\ TEL +49 641 7950090
(;O/ \/ \O;)
