>>> On 2010-12-02 at 08:44, wrote:
> what is the difference between using /bin/sh and /bin/bash?
It's morning, so I feel like rambling:
/bin/bash, if it exists, presumably can always be assumed to be Bash, the GNU
"Bourne-Again" Shell. Hopefully some relatively recent version of it.
On some U
what is the difference between using /bin/sh and /bin/bash?
On 12/2/10 4:35 AM, Suren wrote:
Hey Kendy,
The new portability stuff added to autogen.sh works fine for me now(
in /bin/sh itself that is).
Regards,
~Suren
On 12/02/2010 04:49 AM, Jan Holesovsky wrote:
Hi Julien,
On 2010-12-01 a
Le 02/12/2010 00:19, Jan Holesovsky a écrit :
Hi Julien,
On 2010-12-01 at 23:26 +0100, Julien Nabet wrote:
I've runned autogen.sh present in rawbuild and i've got : Bad substitution.
After having added a set -x at the beginning of the script, I found it
was in the function requote, all the
Hey Kendy,
The new portability stuff added to autogen.sh works fine for me now( in
/bin/sh itself that is).
Regards,
~Suren
On 12/02/2010 04:49 AM, Jan Holesovsky wrote:
Hi Julien,
On 2010-12-01 at 23:26 +0100, Julien Nabet wrote:
I've runned autogen.sh present in rawbuild and i've got :
Hi Julien,
On 2010-12-01 at 23:26 +0100, Julien Nabet wrote:
> I've runned autogen.sh present in rawbuild and i've got : Bad substitution.
> After having added a set -x at the beginning of the script, I found it
> was in the function requote, all these lines are ko :
>
> set -- "${@//\'
Hello,
I've runned autogen.sh present in rawbuild and i've got : Bad substitution.
After having added a set -x at the beginning of the script, I found it
was in the function requote, all these lines are ko :
set -- "${@//\'/$q\'$q}"# quote inner instances of '
set -- "${
