Re: The right way to invoke sh from a freebsd makefile?

2013-09-22 Thread Bryan Drewery
On 9/22/2013 6:18 PM, Ian Lepore wrote: What's the right way to launch the bourne shell from a makefile? I had assumed the ${SHELL} variable would be set to the right copy of /bin/sh (like maybe the one in tmp or legacy at various stages). It appears that that's not the case, and ${SHELL} is

Re: The right way to invoke sh from a freebsd makefile?

2013-09-22 Thread Glen Barber
On Sun, Sep 22, 2013 at 05:18:25PM -0600, Ian Lepore wrote: What's the right way to launch the bourne shell from a makefile? I had assumed the ${SHELL} variable would be set to the right copy of /bin/sh (like maybe the one in tmp or legacy at various stages). It appears that that's not the

Re: The right way to invoke sh from a freebsd makefile?

2013-09-22 Thread Ian Lepore
On Sun, 2013-09-22 at 19:27 -0400, Glen Barber wrote: On Sun, Sep 22, 2013 at 05:18:25PM -0600, Ian Lepore wrote: What's the right way to launch the bourne shell from a makefile? I had assumed the ${SHELL} variable would be set to the right copy of /bin/sh (like maybe the one in tmp or

Re: The right way to invoke sh from a freebsd makefile?

2013-09-22 Thread Glen Barber
On Sun, Sep 22, 2013 at 05:37:51PM -0600, Ian Lepore wrote: On Sun, 2013-09-22 at 19:27 -0400, Glen Barber wrote: On Sun, Sep 22, 2013 at 05:18:25PM -0600, Ian Lepore wrote: What's the right way to launch the bourne shell from a makefile? I had assumed the ${SHELL} variable would be set

Re: The right way to invoke sh from a freebsd makefile?

2013-09-22 Thread Ian Lepore
On Sun, 2013-09-22 at 19:45 -0400, Glen Barber wrote: On Sun, Sep 22, 2013 at 05:37:51PM -0600, Ian Lepore wrote: On Sun, 2013-09-22 at 19:27 -0400, Glen Barber wrote: On Sun, Sep 22, 2013 at 05:18:25PM -0600, Ian Lepore wrote: What's the right way to launch the bourne shell from a

Re: The right way to invoke sh from a freebsd makefile?

2013-09-22 Thread Glen Barber
On Sun, Sep 22, 2013 at 05:56:07PM -0600, Ian Lepore wrote: You can hard-code /bin/sh directly, but what I was getting at with the '#!/usr/bin/env sh' is that the 'sh' interpreter of the build environment could be used (instead of /bin/sh directly). Then you don't need to worry about the