[patch] Use /bin/bash instead of /bin/sh for bashisms
Peter S. Mazinger
ps.m at gmx.net
Tue Jan 3 10:54:09 UTC 2006
On Tue, 3 Jan 2006, Jan-Benedict Glaw wrote:
> On Mon, 2006-01-02 21:40:25 -0500, John Kelly <jakelly at shtc.net> wrote:
> > On Mon, 02 Jan 2006 10:49:27 +0100, Natanael Copa <mlists at tanael.org>
> > >It didn't work with csh and tcsh.
> > That's irrelevant.
> > http://www.faqs.org/faqs/unix-faq/shell/csh-whynot/
> Well, the main point is that the scripts are just used to build the
> library. Reading POSIX, you *can* *not* rely on /bin/sh being a POSIX
> shell. That is, you cannot rely on the shellbang. You *have* to call
> scripts like 'sh myscript.sh' to get "proper" execution, but that's
> not done in all places.
> The reminder is, either fix the build system to "correctly" call all
> scripts, or just use constructs that work in all shells. ...and in the
> cases pointed out, there's no csh-specific problems.
> So explicitely writing for csh is probably just dumb, but throwing
> away compatibility for no good reason is as well :)
> MfG, JBG
the script does not have anything to do with the build system and not
meant for any user, it is only a maintainance script I added to allow me
to update all Makefiles in one step, I could as well remove it from the
Peter S. Mazinger <ps dot m at gmx dot net> ID: 0xA5F059F2
Key fingerprint = 92A4 31E1 56BC 3D5A 2D08 BB6E C389 975E A5F0 59F2
More information about the uClibc