Roland Mainz <[EMAIL PROTECTED]> wrote:
> > > Erm, the problem we have is that all new Makefiles in the
> > > ksh93-integration prototype004 tree use SHELL=/bin/ksh to simplify some
> >
> > If you take your ideas of being as POSIX compliant as possible, you should
> > not put SHELL=/bin/ksh into a Makefile as it makes the makefile
> > non-portable.
>
> What else would you suggest ? If we would (theoretically) want the
> ultimate "portabilty" we would have to resurrect the "Thomson shell" (it
> even predates the original Bourne shell) and use that for everything (I
> don't even try to imagine the horror... =:-) ).
SunOS was never delivered wth that shell, as it has been first published past
1975.
> When I say "portable" I think about "portable" with POSIX as basis with
> some extensions which includes something to set a POSIX-like shell. In
> theory SHELL=/usr/xpg4/bin/sh would be the correct choice in this case,
> right ?
No, POSIX is a source standard that does explicitly exclude path names.
If you think POSIX, you should not use absolute path names, in special if you
are trying to use something that is related to a path name that currently does
not exist on Solaris.
If you really believe that you need features in a Makefile that are not
available with the Bourne shell, you should explain this.
And please note that I mentioned that dmake in most cases avoids to call SHELL
which saves much more time than a few calls to shell builtins might do.
Jörg
--
EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin
[EMAIL PROTECTED] (uni)
[EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/
URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily
_______________________________________________
opensolaris-code mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/opensolaris-code
