On Thu, 17 Aug 2006 19:26:21 +0200 Josh Hurst wrote:
> On 8/17/06, David Korn <dgk at research.att.com> wrote:
> > cc: joshhurst at gmail.com
> > Subject: Re: Re: [ksh93-integration-discuss] Re: Minor fix for
> > ksh93r+_alpha_20060724 tests/exit.sh...
> > --------
> > > getconf LIBPATH returns an error on Linux. How is this supposed to work?
> > The ksh93 getconf builtin should work on linux.
> OK, my fault. However I still do not see how it should help. getconf
> LIBPATH returns
> lib:LD_LIBRARY_PATH
> while Roland's patch was adding LD_LIBRARY_PATH_32 and
> LD_LIBRARY_PATH_64 which are different entities than LD_LIBRARY_PATH.
> Solaris is an operating system which can execute both 32bit and 64bit
> applications where LD_LIBRARY_PATH_32 affects only 32bit applications
> while LD_LIBRARY_PATH_64 is for 64bit applications only.
> If I understand April's and Roland's plans correctly they are planning
> to ship BOTH 32bit and 64bit versions of ksh93 simultaneously in
> Solaris which means that getconf LIBPATH is inappropriate in this case
ast getconf LIBPATH on 64 bit solaris will configure to
lib/sparcv9:LD_LIBRARY_PATH_64:sol.*64*,lib:LD_LIBRARY_PATH,lib:LD_LIBRARY_PATH_32
and the ksh93 exit.sh test will get the env var names from that
( LD_LIBRARY_PATH_64 LD_LIBRARY_PATH LD_LIBRARY_PATH_32 )
I originally extended ast getconf LIBPATH to handle a similar situation on sgi
so it was only the LIBPATH configure for solaris that needed fixing
(along with the one time change to the ksh93 exit.sh test)
-- Glenn Fowler -- AT&T Research, Florham Park NJ --
