On Thu, Jul 3, 2008 at 4:50 PM, Alan Coopersmith
<[EMAIL PROTECTED]> wrote:
> Dan Nicholson wrote:
>> Oh, we should probably be setting SHELL in configs/autoconf all the
>> time. Autoconf has support for this by using the shell that configure
>> was called with or the value of CONFIG_SHELL.
>>
>> Do you know which parts are too POSIXy? I don't think it would be too
>> much work to make the build work with any reasonable Bourne shell.
>
> I don't remember off hand which part of the shell commands in the Makefile
> needed this - the common errors with the Solaris /bin/sh are use of things
> like $() instead of ``, use of [[ ]] tests instead of [ ], use of == instead
> of =,  use of the test/[] flags listed as "Not in /bin/sh" on
> http://docs.sun.com/app/docs/doc/816-5165/test-1?a=view
> and other features invented in the almost 20 years since SVR4's bourne
> shell was last updated.   (As Roland noted, this is being fixed in OpenSolaris
> by replacing /bin/sh with ksh93, and future Solaris releases may do the same,
> but that doesn't help users of past/current Solaris releases.)

Alan, I just pushed a match that removes the EXTRA_CONFIG_LINES
setting, but keeps the POSIX_SHELL checks for Solaris. I simulated it
on Linux and it works correctly for me, but you may want to check. See
here:

http://cgit.freedesktop.org/mesa/mesa/commit/?id=bfb27b5fc020437d95b1185f0fce850209744d92

--
Dan

-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
Mesa3d-dev mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mesa3d-dev

Reply via email to