Getting Started with RTEMS for C/C++ Users
NOTE: This step is required if building BINUTILS, GCC, and NEWLIB using the procedures described in Using configure and make or Using the bit Script. 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-2.95.2
zcat ../../archive/gcc-2.95.2-rtems-20000606.diff.gz | \
patch -p1
Check to see if any of these patches have been rejected using the following sequence:
cd tools/gcc-2.95.2 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.
Apply the patch using the following command sequence:
cd tools/binutils-2.9.5.0.24
zcat ../../archive/binutils-2.9.5.0.24-rtems-20000207.diff.gz | \
patch -p1
Check to see if any of these patches have been rejected using the following sequence:
cd tools/binutils-2.9.5.0.24 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.
Apply the patch using the following command sequence:
cd tools/newlib-1.8.2
zcat ../../archive/newlib-1.8.2-rtems-20000606.diff.gz | \
patch -p1
Check to see if any of these patches have been rejected using the following sequence:
cd tools/newlib-1.8.2 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 for C/C++ Users
Copyright © 1988-2000 OAR Corporation