gcc-3.4.3-ssp-3.patch offset patches?

Randy McMurchy randy at linuxfromscratch.org
Thu Mar 24 12:11:55 PST 2005

Archaic wrote these words on 03/24/05 14:03 CST:

> And to further ease your concern, there is absolutely no harm in fuzz.
> It just means the *identical* lines to be replace exist, but not at the
> exact same line number.


I always thought fuzz meant something other than just changing
of the line numbers. Take the following example:

patching file lib/kadm5/Makefile.in
Hunk #1 succeeded at 268 (offset 144 lines).
patching file lib/kadm5/password_quality.c
Hunk #1 succeeded at 32 with fuzz 2.

What is the difference between just being offset versus having fuzz?

(note: I realize it's okay to have fuzz and that the patch
installs completely, I'm just trying to figure out what exactly
fuzz means)


rmlscsi: [GNU ld version 20041220] [gcc (GCC) 3.4.3]
[GNU C Library stable release version 2.3.4] [Linux 2.6.10 i686]
14:08:00 up 22 days, 12 min, 10 users, load average: 0.39, 0.93, 0.79

More information about the hlfs-dev mailing list