Fwd: strange behaviour when running a script via "run"
Carlo de Falco
carlo.defalco at gmail.com
Wed Apr 22 08:07:19 CDT 2009
I forgot to add the list to the receipients...
c.
Begin forwarded message:
> From: Carlo de Falco <carlo.defalco at gmail.com>
> Date: 22 April 2009 09:40:25 GMT+02:00
> To: John W. Eaton <jwe at octave.org>
> Subject: Re: strange behaviour when running a script via "run"
>
>
> On 21 Apr 2009, at 15:47, John W. Eaton wrote:
>
>> On 21-Apr-2009, Carlo de Falco wrote:
>>
>> | BTW I had to apply the patch manually as I wasn't able to do it
>> | automatically,
>>
>> What commands did you try?
>
> patch < diffs
>
> and
>
> patch -p1 < diffs
>
>> | what would be the correct procedure to apply a patch in that
>> format?
>>
>> In the top-level Octave source directory, you should be able to run
>>
>> patch < diffs
>
> this gave me the following:
>
> patch < diffs
> can't find file to patch at input line 4
> Perhaps you should have used the -p or --strip option?
>
> while using the -p1 option produced the following:
>
> $ patch -p1 < diffs
> patching file src/mex.cc
> Hunk #1 FAILED at 3271.
> Hunk #2 FAILED at 3283.
> 2 out of 2 hunks FAILED -- saving rejects to file src/mex.cc.rej
> patching file src/parse.y
> Hunk #1 FAILED at 4171.
> Hunk #2 succeeded at 4196 with fuzz 2.
> 1 out of 2 hunks FAILED -- saving rejects to file src/parse.y.rej
> patching file src/toplev.cc
> patch: **** malformed patch at line 73: }
>
>> jwe
>
> c.
>
More information about the Bug-octave
mailing list