John Bolton wrote: > > I’m on this step and applying patch gcc-4.4.1-pure64-1.patch results > in the following failures: > > > > root:/sources/gcc-4.4.1# patch -Np1 -i ../gcc-4.4.1-pure64-1.patch > > patching file gcc/config/i386/linux64.h > > patching file gcc/config/i386/t-linux64 > > patching file gcc/config/linux.h > > patching file gcc/config/mips/linux64.h > > patching file gcc/config/mips/t-linux64 > > patching file gcc/config/rs6000/linux64.h > > patching file gcc/config/rs6000/t-linux64 > > Hunk #1 FAILED at 19. > > 1 out of 1 hunk FAILED -- saving rejects to file > gcc/config/rs6000/t-linux64.rej > > patching file gcc/config/s390/linux.h > > patching file gcc/config/s390/t-linux64 > > patching file gcc/config/sparc/linux64.h > > Hunk #2 FAILED at 121. > > Hunk #3 FAILED at 130. > > Hunk #4 FAILED at 211. > > 3 out of 4 hunks FAILED -- saving rejects to file > gcc/config/sparc/linux64.h.rej > > patching file gcc/config/sparc/linux.h > > Hunk #1 FAILED at 86. > > 1 out of 1 hunk FAILED -- saving rejects to file > gcc/config/sparc/linux.h.rej > > patching file gcc/config/sparc/t-linux64 > > root:/sources/gcc-4.4.1# > > > > Does anybody have a solution for this problem? I am using the LFS CD > as my host operating system. > > > > Thanks, > > > > John Bolton > Probably a conflict with the branch update patch. Unless you're building for sparc / rs6000 this shouldn't be an issue.
_______________________________________________ Clfs-support mailing list [email protected] http://lists.cross-lfs.org/listinfo.cgi/clfs-support-cross-lfs.org
