On Sun, Jun 29, 2008 at 7:44 PM, Roland Mainz <[EMAIL PROTECTED]> wrote: > Dan Nicholson wrote: > >> 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. > > The problem is that Solaris's old /usr/bin/sh is really the old Bourne > shell and not "bash" - which means even basic POSIX shell functionality > like $(...) is not available and stuff like IFS field splitting won't > work reliable.
I'm pretty aware what the difference are (and that Bourne != bash), I was just wondering if we could track down the places in mesa where they occur. I know when I wrote configure.ac I tried hard to make it Bourne compatible (although there is some IFS splitting on --with-demos that might be sketchy). I imagine most of the issue would be in bin/mklib and bin/minstall, but I haven't checked. Also, there is a port of the Solaris Bourne shell for Linux: the Heirloom shell. I find it useful for testing shell portability. http://heirloom.sourceforge.net/sh.html Anyway, even if we keep the POSIX shell checks for Solaris, we should still be substituting for SHELL on all platforms so make runs the shell the user wants. -- Dan ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ Mesa3d-dev mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mesa3d-dev
