On 4/9/14, 8:47 PM, Linda Walsh wrote:
>
>
> Chet Ramey wrote:
>> Bash-Release: 4.3
>> Patch-IDs: bash43-00{3..8}
> -----------------
>
> Chet, patches 1 and 2 applied with no problems:
> but 3-8 don't follow the same pattern and give warnings no
> matter what:
>
>> i=1;patch <../bash-4.3-patches/bash43-00$i
> patching file test.c
> patching file patchlevel.h
> Ishtar:tools/bash/bash-4.3> i=2;patch <../bash-4.3-patches/bash43-00$i
> patching file trap.c
> patching file patchlevel.h
> Ishtar:tools/bash/bash-4.3> i=3;patch <../bash-4.3-patches/bash43-00$i
> can't find file to patch at input line 20
> Perhaps you should have used the -p or --strip option?...
> ---
> so tried -p0 (which supposedly says don't strip any leading slashes, --
> which I thought was the default?)
They apply cleanly on my systems using patch -p0. I'm not sure what
version of patch you're using, but the bash patches have always been
issued with relative paths beginning with `..' like that.
(And, incidentally, patches 1 and 2, which you said applied cleanly,
use the same form of relative pathnames.)
Chet
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, ITS, CWRU [email protected] http://cnswww.cns.cwru.edu/~chet/
