Merged changes from 4.5 branch and removed that branch.

This commit is contained in:
Joel Sherrill
2000-04-25 13:15:14 +00:00
parent 0765f9be43
commit bb4b574983
11 changed files with 152 additions and 47 deletions

View File

@@ -67,15 +67,6 @@ 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.
To see the files that have been modified use the sequence:
@example
cd tools/@value{GDB-UNTAR}
find . -name "*.orig" -print
@end example
The files that are found, have been modified by the patch file.
@end ifset
@section Using the bit_gdb script

View File

@@ -127,13 +127,14 @@ use to RTEMS users.
@subsection RTEMS Mailing List
rtems-list@@OARcorp.com
rtems-users@@OARcorp.com
This mailing list is dedicated to discussion of issues related
to RTEMS. If you have questions about RTEMS, wish to make
suggestions, or just want to pick up hints, this is a good
list to subscribe to. Subscribe by sending a message with
the one line "subscribe" to rtems-list-request@@OARcorp.com.
This mailing list is dedicated to the discussion of issues related
to RTEMS, including GNAT/RTEMS. If you have questions about RTEMS,
wish to make suggestions, or just want to pick up hints, this is a
good list to subscribe to. Subscribe by sending an empty mail
message to rtems-users-subscribe@@OARcorp.com. Messages sent
to rtems-users@@OARcorp.com are posted to the list.
@subsection CrossGCC Mailing List

View File

@@ -36,9 +36,12 @@ Use the following command to start the build of the sample application:
@example
cd tools/hello_world_c
gmake
make
@end example
NOTE: GNU make is the preferred @code{make} utility. Other @code{make}
implementations may work but all testing is done with GNU make.
If no errors are detected during the sample application build, it is
reasonable to assume that the build of the GNU C/C++ Cross Compiler Tools
for RTEMS and RTEMS itself for the selected host and target
@@ -50,7 +53,7 @@ If the sample application has successfully been build, then the application
executable is placed in the following directory:
@example
tools/hello_world_c/o-<BOARD_SUPPORT_PACKAGE>/<filename>.exe
tools/hello_world_c/o-optimize/<filename>.exe
@end example
How this executable is downloaded to the target board is very dependent