RE: [avr-gcc-list] avr-gcc toolchain: applying WINAVR patches for Linux box

[Eric Weddington]

> -----Original Message-----
> From:
> address@hidden
> [mailto:address@hidden
> org] On Behalf Of Chunhua Li
> Sent: Sunday, July 15, 2007 10:43 AM
> To: address@hidden
> Subject: [avr-gcc-list] avr-gcc toolchain: applying WINAVR
> patches for Linux box
>
> I recently built avr-gcc on my Linux box, following the
> instructions on
> page
> http://www.nongnu.org/avr-libc/user-manual/install_tools.html. The
> building process is successful, but I have two questions to ask here.
> 1. How do I read the info page/man page, or other documents about
> avr-libc on linux builds?
> 2. I applied patches for gcc-4.2.0, but I don't know whether the
> patching is successful or not because I got a lot of "hunks" from the
> output of "patch -p0". See below.
>
> I downloaded winavr patches from
> http://winavr.cvs.sourceforge.net/winavr/patches
> and applied all patches for gcc-4.2.0. The patch files I used for
> gcc-4.2.0 are
> gcc/4.2.0/10-gcc-4.2.0-c-incpath.patch
> gcc/4.2.0/11-gcc-4.2.0-exec-prefix.patch
> gcc/4.2.0/20-gcc-4.2.0-libiberty-Makefile.in.patch
> gcc/4.2.0/30-gcc-4.2.0-binary-constants.patch
> gcc/4.2.0/40-gcc-4.2.0-bug-28902.patch
> gcc/4.2.0/41-gcc-4.2.0-bug-10768.patch
> gcc/4.2.0/51-gcc-4.2.0-mega256-v2.patch

Please read the README file that also comes with the patches it describes
the numbering system used and whether you should use certain patches. For
your case you do NOT want to use any 0x or 1x patches. So do NOT use these
patches:

gcc/4.2.0/10-gcc-4.2.0-c-incpath.patch
gcc/4.2.0/11-gcc-4.2.0-exec-prefix.patch

As they are specific to MinGW (Windows) hosts.


> I wrote a script and and automated the building process and
> log all of
> outputs. From my log file I got the following information
> when I applied
> patch for gcc-4.2.0
> <---------------------------------------------------------------->
> Applying patch
> /home/chunhua/slackware/source/avrgcc/patches/gcc/4.2.0/10-gcc
> -4.2.0-c-incpath.patch
> patching file gcc/c-incpath.c
> Hunk #1 succeeded at 340 with fuzz 1 (offset 9 lines).
> Applying patch
> /home/chunhua/slackware/source/avrgcc/patches/gcc/4.2.0/11-gcc
> -4.2.0-exec-prefix.patch
> patching file gcc/gcc.c
> Hunk #1 succeeded at 3370 with fuzz 1 (offset 120 lines).
> Hunk #2 succeeded at 6092 (offset -54 lines).
> patching file gcc/prefix.c
> patching file gcc/toplev.c
> Hunk #2 succeeded at 1480 (offset 45 lines).
> Applying patch
> /home/chunhua/slackware/source/avrgcc/patches/gcc/4.2.0/20-gcc
> -4.2.0-libiberty-Makefile.in.patch
> patching file libiberty/Makefile.in
> Hunk #1 succeeded at 334 with fuzz 2 (offset 59 lines).
> Applying patch
> /home/chunhua/slackware/source/avrgcc/patches/gcc/4.2.0/30-gcc
> -4.2.0-binary-constants.patch
> patching file ./gcc/doc/extend.texi
> Hunk #1 succeeded at 81 (offset 2 lines).
> Hunk #2 succeeded at 10371 (offset 628 lines).
> patching file ./libcpp/include/cpplib.h
> Hunk #1 succeeded at 744 (offset 15 lines).
> patching file ./libcpp/expr.c
> Hunk #1 succeeded at 182 (offset 11 lines).
> Hunk #3 succeeded at 325 (offset 20 lines).
> Hunk #5 succeeded at 445 (offset 20 lines).
> Applying patch
> /home/chunhua/slackware/source/avrgcc/patches/gcc/4.2.0/40-gcc
> -4.2.0-bug-28902.patch
> patching file gcc/config/avr/avr.h
> Hunk #1 succeeded at 96 (offset 2 lines).
> Applying patch
> /home/chunhua/slackware/source/avrgcc/patches/gcc/4.2.0/41-gcc
> -4.2.0-bug-10768.patch
> patching file gcc/ada/uintp.ads
> patching file gcc/ada/types.h
> Applying patch
> /home/chunhua/slackware/source/avrgcc/patches/gcc/4.2.0/51-gcc
> -4.2.0-mega256-v2.patch
> patching file gcc/config/avr/libgcc.S
> patching file gcc/config/avr/avr.md
> patching file gcc/config/avr/avr.c
> patching file gcc/config/avr/t-avr
> patching file gcc/config/avr/avr.h
> Hunk #4 succeeded at 641 (offset 1 line).
> Hunk #6 succeeded at 805 (offset 1 line).
> <-------------------------------------------------------------
> --------->
>
> You can see lots of "Hunks" here. I don't understand what the
> hunks mean

Read the documentation on "diffutils" (IIRC) as it contains the
documentation on the "patch" utility. This will help you understand what
they mean.

> here, but I want to know if the patches were applied successfully?

Did you get any errors? If not, ergo you were successful.

Eric Weddington