Comment 41 for bug 697039

Tobi (TORO) already mentioned the thread <http://groups.google.com/group/hugin-ptx/browse_thread/thread/b18eaae2c7e21a80?pli=1>.
There it is mentioned that it might be an issue with the shell being used.

I assumed that bash was the shell used by all Leopard users and this was backed up by one user who tested my request (to do a set | grep SHELL wich resulted in a SHELL=/bin/bash ).
Today I got a offline message of a user who mentioned that his Leopard uses the tcsh shell.

Can we somehow create a patch that forces the the shell to be bash in the Makefile (at least for OSX). I already created myself a patch that did write to the makefile a:
1) #!/bin/bash as first line
2) write a line SHELL=/bin/bash in the "Tool configuration" section
3) did both 1) and 2)

These options didn't seem to work, but I'm not a programmer and could be doing it completely wrong. I would appreciate it if a programmer could have a look at it.

However, I'm also looking into another direction now (4): On OSX we bundle gnumake inside the bundle as we are dealing with different sets of make on OSX. Could it be neccessary to write a patch to both the makefile and the code for the OSX bundle to add a line to the "Tool configuration" section:
make=<path>/gnumake (identical to enblend/enfuse/PT*), so that Hugin knows which (gnu)make to use. I can add this line to the makefile, but I have no idea how it is called from hugin and at which positions. I'm afraid a programmer needs to do this (please).

So concluding:
Are 1), 2), 3) worth looking into?
Is (4) and option?