Programming :: Patch Command: Hunk #1 Succeeded At 25 With Fuzz 1

I am beginning to start to work with compiling and I get some confusing output adding patches to sourcecode (xosview-1.8.3). (The patch is for suppressing warnings while running the make command : deprecated conversion from * char to ** char ) Xosview compiles without the patch. The patch itself contains 17 files to add mostly const char instead of char. It is one single file containing also files in one subdirectory.
While running `patch < PATCHFILE.patch I had to copy'n'paste the filenames of the subdirectory to the terminal to keep it going. To get it going without much manual input I split it up for the two directories. I got the original patch and both splitted patches succeeding but with confusing output like :

patch unexpectedly ends in middle of line Hunk #2 succeeded at 78 with fuzz 1.

or just

patching file nfsmeter.h patch unexpectedly ends in middle of line # I splitted the original patch to every 17 files and this kind of output I get now at almost every patchfile. I downloaded patch source from debian
and running `pfind` (Puppy-linux speciality .sh) for search text in files showed off patch.c

Quote:
if (verbosity != SILENT)
say ("Hunk #%d FAILED at %s.
", hunk,
format_linenum (numbuf, newwhere));
} else {
if (verbosity == VERBOSE
[Code]........

As you can see the patch is working but what would I have to add to the patch? I added more newlines , added all lines to close a "{" if the patched line was inside ( also added "}" ), adjusted the path at the diff -uraNd /PATH/ -line, even deleted the diff line.