In regard to: Re: ksh bug on Tru64 UNIX causes current libtool failure,...:
On Wed, May 18, 2005 at 05:34:45PM -0500, Tim Mooney wrote:
In regard to: Re: ksh bug on Tru64 UNIX causes current libtool failure,...:
And for possible workarounds: Does Tru64 ship another shell suitable
for use as CONFIG_SHELL? Please try with
CONFIG_SHELL=/bin/foosh /bin/foosh path/to/libtool/configure [OPTIONS]
You might try /usr/bin/posix/sh . I'm not sure if it's "suitable";
hopefully libtool's configure can determine that?
$ ls -ldi /bin/ksh /usr/bin/posix/sh
3380 -rwxr-xr-x 2 bin bin 274400 Feb 7 2003 /bin/ksh
3380 -rwxr-xr-x 2 bin bin 274400 Feb 7 2003 /usr/bin/posix/sh
:-| Thanks for pointing that out Albert. I had never noticed it.
I suppose it's possible that the shell acts differently based on what its
argv[0] is, but that's pretty unlikely.
Tim
--
Tim Mooney [EMAIL PROTECTED]
Information Technology Services (701) 231-1076 (Voice)
Room 242-J6, IACC Building (701) 231-8541 (Fax)
North Dakota State University, Fargo, ND 58105-5164
_______________________________________________
http://lists.gnu.org/mailman/listinfo/libtool
