On 13/10/12 20:10, San blue wrote:
> Hi Colleagues,
>
> When i'm executing the patch for Binutils-2.22, i'm getting the below error :
>
> ----------------------------------------------------------------------
> lfs:/mnt/lfs/tools$ patch -Np1 -i ../sources/binutils-2.22-build_fix-1.patch
> can't find file to patch at input line 11
> Perhaps you used the wrong -p or --strip option?
> The text leading up to this was:
> --------------------------
> |Submitted By:            Matt Burgess<matthew_at_linuxfromscratch_dot_org>
> |Date:                    2012-03-27
> |Initial Package Version: 2.22
> |Upstream Status:         From Upstream
> |Origin:
> http://lists.gnu.org/archive/html/bug-binutils/2011-10/msg00241.html
> |Description:             Fixes a build failure when using -O3 compiler flag
> |
> |diff -Naur binutils-2.22.orig/opcodes/ChangeLog 
> binutils-2.22/opcodes/ChangeLog
> |--- binutils-2.22.orig/opcodes/ChangeLog       2011-11-21
> 09:29:39.000000000 +0000
> |+++ binutils-2.22/opcodes/ChangeLog    2012-03-27 19:49:36.299866714 +0000
> --------------------------
> File to patch:
> Skip this patch? [y]
> Skipping patch.
> 1 out of 1 hunk ignored
> can't find file to patch at input line 26
> Perhaps you used the wrong -p or --strip option?
> The text leading up to this was:
> --------------------------
> |diff -Naur binutils-2.22.orig/opcodes/i386-dis.c
> binutils-2.22/opcodes/i386-dis.c
> |--- binutils-2.22.orig/opcodes/i386-dis.c      2011-08-02
> 19:58:06.000000000 +0000
> |+++ binutils-2.22/opcodes/i386-dis.c   2012-03-27 19:48:28.447812481 +0000
> --------------------------
> File to patch:
> Skip this patch? [y]
> Skipping patch.
> 1 out of 1 hunk ignored
>
> -----------------------------------------------------------------
>
>
> Please suggest me what can be done to solve this issue ? or does it
> really required ?
>
> Best regards, San
What dir are you in when you run the command??
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Reply via email to