On 1 October 2012 22:49, Eric Blake wrote:
> therefore, there are TWO 'line 1' locations within the release-prep
> rule, because there are two shells spawned.
Didn't spot the lack of continuation, which, as it turned out, was
precisely the opposite of the bug I'd introduced. I must be
backslash-b
On 10/01/2012 02:03 PM, Reuben Thomas wrote:
> On 1 October 2012 20:37, Jim Meyering wrote:
>> Reuben Thomas wrote:
>>> I get the following error while trying to make a GNU Zile release:
>>>
>>> /bin/bash: -c: line 1: syntax error near unexpected token `then'
>>> /bin/bash: -c: line 1: `@if test -
Reuben Thomas wrote:
> On 1 October 2012 20:37, Jim Meyering wrote:
>> Reuben Thomas wrote:
>>> I get the following error while trying to make a GNU Zile release:
>>>
>>> /bin/bash: -c: line 1: syntax error near unexpected token `then'
>>> /bin/bash: -c: line 1: `@if test -d ../release; then \'
>
Wait, I got it. I managed to splice two lines that shouldn't be
spliced when making a small edit to maint.mk.
Sorry for the noise.
--
http://rrt.sc3d.org
On 1 October 2012 20:37, Jim Meyering wrote:
> Reuben Thomas wrote:
>> I get the following error while trying to make a GNU Zile release:
>>
>> /bin/bash: -c: line 1: syntax error near unexpected token `then'
>> /bin/bash: -c: line 1: `@if test -d ../release; then \'
>> make[2]: *** [release-prep
Reuben Thomas wrote:
> I get the following error while trying to make a GNU Zile release:
>
> /bin/bash: -c: line 1: syntax error near unexpected token `then'
> /bin/bash: -c: line 1: `@if test -d ../release; then \'
> make[2]: *** [release-prep] Error 1
>
> I'm using bash 4.2.24(1)-release as shi
