Getting Started with RTEMS
NOTE: This step is required if building BINUTILS, GCC, and NEWLIB using the procedures described in Using configure and make. It is NOT required if using the procedure described in Using RPM to Build BINUTILS GCC and NEWLIB.
This section describes the process of applying the RTEMS patches to GCC, NEWLIB, and BINUTILS.
Apply the patch using the following command sequence:
cd tools/gcc-3.2.3
cat ../../archive/gcc-3.2.3-rtems-20040108.diff | \
patch -p1
If the patch was compressed with the gzip program, it will
have a suffix of .gz and you should use zcat instead
of cat as shown above. If the patch was compressed with
the gzip program, it will have a suffix of .bz2 and
you should use bzcat instead of cat as shown above.
Check to see if any of these patches have been rejected using the following sequence:
cd tools/gcc-3.2.3 find . -name "*.rej" -print
If any files are found with the .rej extension, a patch has been rejected. This should not happen with a good patch file which is properly applied.
No RTEMS specific patches are required for binutils-2.13.2.1 to support RTEMS 4.6.0.
Apply the patch using the following command sequence:
cd tools/newlib-1.11.0
cat ../../archive/newlib-1.11.0-rtems-20030605.diff | \
patch -p1
If the patch was compressed with the gzip program, it will
have a suffix of .gz and you should use zcat instead
of cat as shown above. If the patch was compressed with
the gzip program, it will have a suffix of .bz2 and
you should use bzcat instead of cat as shown above.
Check to see if any of these patches have been rejected using the following sequence:
cd tools/newlib-1.11.0 find . -name "*.rej" -print
If any files are found with the .rej extension, a patch has been rejected. This should not happen with a good patch file which is properly applied.
Getting Started with RTEMS
Copyright © 1988-2004 OAR Corporation