Hi Bob,

I also got the same result: every hunk was rejected. Rather than fight it, I just manually applied the patches--it only took a couple of minutes. This was one of those rare cases where I could do it by hand faster than having the malfunctioning tools do it. ;)

Kevin

Bob McCown wrote:
Thanks for the reply, Wei.

I had thought so, but when I ran it against the 5.2.1 source tree, I
received the following errors:

finagle:~/Desktop/cryptopp521 % patch < crypto521gcc4patch
patching file iterhash.h
Hunk #1 FAILED at 88.
1 out of 1 hunk FAILED -- saving rejects to file iterhash.h.rej
patching file lubyrack.h
Hunk #1 FAILED at 38.
1 out of 1 hunk FAILED -- saving rejects to file lubyrack.h.rej
patching file seckey.h
Hunk #1 FAILED at 21.
Hunk #2 FAILED at 31.
Hunk #3 FAILED at 50.
3 out of 3 hunks FAILED -- saving rejects to file seckey.h.rej
patching file dll.cpp
Hunk #1 FAILED at 1.
Hunk #2 FAILED at 37.
2 out of 2 hunks FAILED -- saving rejects to file dll.cpp.rej
finagle:~/Desktop/cryptopp521 %

Reply via email to