Changeset c1c5ab9 in rtems


Ignore:
Timestamp:
Apr 14, 1998, 2:05:10 PM (23 years ago)
Author:
Joel Sherrill <joel.sherrill@…>
Branches:
4.10, 4.11, 4.8, 4.9, 5, master
Children:
513196f
Parents:
757a75d
Message:

Comments from Chris Johns

Location:
doc
Files:
4 edited

Legend:

Unmodified
Added
Removed
  • doc/started/buildrt.t

    r757a75d rc1c5ab9  
    3030@end example
    3131
    32 NOTE:  The above command is in Bourne shell (@code{sh}) syntax and should work with
    33 the Korn (@code{ksh}) and GNU Bourne Again Shell (@code{bash}).  It will not
    34 work with the C Shell (@code{csh})or derivatives of the C Shell.
     32NOTE:  The above command is in Bourne shell (@code{sh}) syntax and
     33should work with the Korn (@code{ksh}) and GNU Bourne Again Shell
     34(@code{bash}).  It will not work with the C Shell (@code{csh}) or
     35derivatives of the C Shell.
     36
     37@section Verifying the Operation of the Cross Toolset
     38
     39In order to insure that the cross-compiler is invoking the correct
     40subprograms (like @code{as} and @code{ld}), one can test assemble
     41a small program.  When in verbose more, @code{gcc} prints out information
     42showing where it found the subprograms it invokes.  Place the following
     43function in a file named @code{f.c}:
     44
     45@example
     46int f( int x )
     47{
     48  return x + 1;
     49}
     50@end example
     51
     52Then assemble the file using a command similar to the following:
     53
     54@example
     55m68k-rtems-gcc -v -S f.c
     56@end example
     57
     58Where @code{m68k-rtems-gcc} should be changed to match the installed
     59name of your cross compiler.  The result of this command will be
     60a sequence of output showing where the cross-compiler searched for
     61and found its subcomponents.  Verify that these paths correspond
     62to your <INSTALL_POINT>.
     63
     64@b{NOTE:} One of the most common installation errors is for the
     65cross-compiler not to be able to find the cross assembler and default
     66to using the native @code{as}.  This can result in very confusing
     67error messages.
    3568
    3669@section Generate RTEMS for a Specific Target and BSP
  • doc/started/intro.t

    r757a75d rc1c5ab9  
    131131
    132132This mailing list is dedicated to discussion of issues related
    133 to RTEMS.  If you have questions about RTEMS, which to make
     133to RTEMS.  If you have questions about RTEMS, wish to make
    134134suggestions, or just want to pick up hints, this is a good
    135135list to subscribe to.  Subscribe by sending a message with
  • doc/started_ada/buildrt.t

    r757a75d rc1c5ab9  
    3333work with the Korn (@code{ksh}) and GNU Bourne Again Shell (@code{bash}). 
    3434It will not work with the C Shell (@code{csh})or derivatives of the C Shell.
     35
     36@section Verifying the Operation of the Cross Toolset
     37
     38In order to insure that the cross-compiler is invoking the correct
     39subprograms (like @code{as} and @code{ld}), one can test assemble
     40a small program.  When in verbose more, @code{gcc} prints out information
     41showing where it found the subprograms it invokes.  Place the following
     42function in a file named @code{f.c}:
     43
     44@example
     45int f( int x )
     46{
     47  return x + 1;
     48}
     49@end example
     50
     51Then assemble the file using a command similar to the following:
     52
     53@example
     54m68k-rtems-gcc -v -S f.c
     55@end example
     56
     57Where @code{m68k-rtems-gcc} should be changed to match the installed
     58name of your cross compiler.  The result of this command will be
     59a sequence of output showing where the cross-compiler searched for
     60and found its subcomponents.  Verify that these paths correspond
     61to your <INSTALL_POINT>.
     62
     63@b{NOTE:} One of the most common installation errors is for the
     64cross-compiler not to be able to find the cross assembler and default
     65to using the native @code{as}.  This can result in very confusing
     66error messages.
    3567
    3668@section Generate RTEMS for a Specific Target and BSP
  • doc/started_ada/intro.t

    r757a75d rc1c5ab9  
    131131
    132132This mailing list is dedicated to discussion of issues related
    133 to RTEMS.  If you have questions about RTEMS, which to make
     133to RTEMS.  If you have questions about RTEMS, wish to make
    134134suggestions, or just want to pick up hints, this is a good
    135135list to subscribe to.  Subscribe by sending a message with
Note: See TracChangeset for help on using the changeset viewer.