Stephane CHAZELAS <[email protected]> wrote: > 2017-05-24 16:15:03 +0200, Joerg Schilling:
> > A configure script (if done correctly) is a script with _very_ > > pessimistic assumptions on portability. Given that "posh" completely fails > > here, makes it unusable for every day work. > > Without being more specific than a script named "configure", I > can't really help. Even if you mean a GNU autoconf generated > "configure" script, that will still depend on whatever extra > "check" code snipets the developer has haded. This is "Schily configure" that has been build starting with GNU configure-2.13. There are no non-portable parts in the script and any other halfway OK shell has no problems with it. So this is definitely a "posh" problem that would need to be addressed by the posh people before takting posh for serious. > > $ exit > > posh: exit: bad number > > Let's be serious, if "posh" had such a bug it would have been > reported long ago and fixed. Presumably, you've compiled > it in a such way or on such a system that has never been tested > before and triggered a bug. A shell that does not work correctly when compiled from the latest source has a problem. This definitely applies to posh. > to your ~/.zshenv and run your "configure" script as: > > ZSH_EMULATION=sh CONFIG_SHELL=/usr/bin/zsh /usr/bin/zsh ./configure Ok this is what I get: ZSH_EMULATION=sh CONFIG_SHELL=/usr/bin/zsh /usr/bin/zsh ./configure ./configure:777: no matches found: conftest* creating cache ./config.cache ^C./configure:828: no matches found: conftest* Does not look convincing... ^C is as I needed to stop a hang. > > If you like to use the Bourne Shell as Linux default shell, compile it with: > [...] > > As discussed, even with -o posix, in my tests it's still not > POSIX (for instance with regards to the environment processing, > with regards to redirected compound commands being run in > subshells, and $IFS processing at least). I did get one single bugreport from you related to field splitting. Jörg -- EMail:[email protected] (home) Jörg Schilling D-13353 Berlin [email protected] (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.org/private/ http://sf.net/projects/schilytools/files/'
