From: Derek H. <de...@ho...> - 2001-12-11 20:47:46
|
On Tuesday, December 11, 2001, at 01:35 AM, Michael Maibaum wrote: >>> >> More than enough for the compilation. I think the cause for the errors >> was >> libtool using ksh instead of sh in the build. Apparently there is no way >> to >> keep it from switching to Korn shell if only there is a /bin/ksh binary, >> even when I rebuilt fink completely under zsh -- ksh was neither my >> working nor login shell, nor $SHELL in the process. >> Of course the real reason seems to be pdksh being unstable, still this >> behaviour of libtool is rather annoying (I know I am not supposed to put >> non-system binaries into /bin, but generally I *am* using ksh as my >> default shell, so this simplifies my setup somewhat). > > Interestingly, I've started noticing some odd behavior from my system > since I started using ksh....a number of cli apps don't work (for example > screen doesn't work at all under ksh login shell). And as you say, sh > scripts seem to end up calling ksh for reasons I don't understand... > My guess is they are testing if a ksh exists, and in that case prefer it over sh. Which makes some sense on most Unix systems, as ksh is generally more powerful, often also faster than sh, and usually very mature and well tested. Obviously this is not the case with MacOS X and the current status of pdksh, thus it would be nice if the scripts could be patched to avoid this, but I don't have any idea where to start with this. In particular, it seems to vary from package to package, so it might depend on the particular libtool version the package was built with. Derek |