RTOS/rtems
1
0
Fork 0
forked from Imagelibrary/rtems
Code Pull Requests Activity

2004-09-27 Joel Sherrill <joel@OARcorp.com>

Browse Source 
PR 682/misc
	* buildc.t, buildrt.t, sample.t: Fix PATH and tar examples. Enable
	binutils link again.
This commit is contained in:
Joel Sherrill
2004-09-27 22:26:31 +00:00
parent df5f3ca7f5
commit 38d354d335
4 changed files with 23 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
doc/started/ChangeLog
View File

@@ -1,3 +1,15 @@
2004-09-27 Joel Sherrill <joel@OARcorp.com>
PR 682/misc
* buildc.t, buildrt.t, sample.t: Fix PATH and tar examples. Enable
binutils link again.
2004-09-27 Joel Sherrill <joel@OARcorp.com>
PR 682/misc
* buildc.t, buildrt.t, sample.t: Fix PATH and tar examples. Enable
binutils link again.
2004-02-01 Ralf Corsepius <corsepiu@faw.uni-ulm.de>
* binaries.t, buildc.t: Use @value{RTEMSRPMPREFIX} in refs to rpms.

5
doc/started/buildc.t
View File

@@ -498,11 +498,12 @@ invoke the @value{BINUTILSUNTAR} @code{configure} command with the
@code{--help} option.
NOTE: The shell PATH variable needs to be updated to include the path
the binutils has been installed in. This the prefix used above with
the binutils user executables have been installed in. The directory
containing the executables is the prefix used above with
@file{bin} post-fixed.
@example
export PATH=$PATH:@value{RTEMSPREFIX}/bin
export PATH=@value{RTEMSPREFIX}/bin:${PATH}
@end example
Failure to have the binutils in the path will cause the GCC and NEWLIB

15
doc/started/buildrt.t
View File

@@ -20,10 +20,7 @@ placed in your @code{archive} directory.
FTP Site: @value{RTEMSFTPSITE}
Directory: @value{RTEMSFTPDIR}/@value{VERSION}
File: @value{RTEMSTAR}
@ifset use-html
@c URL: @uref{ftp://@value{RTEMSFTPSITE}@value{RTEMSFTPDIR}/@value{VERSION}, Download RTEMS components}
URL: ftp://@value{RTEMSFTPSITE}@value{RTEMSFTPDIR}/@value{VERSION}
@end ifset
URL: @uref{ftp://@value{RTEMSFTPSITE}@value{RTEMSFTPDIR}/@value{VERSION}/@value{RTEMSTAR},,ftp://@value{RTEMSFTPSITE}@value{RTEMSFTPDIR}/@value{VERSION}/@value{RTEMSTAR}}
@end example
@subheading RTEMS Examples including Hello World
@@ -45,7 +42,7 @@ tools directory:
@example
cd tools
tar xzf ../archive/@value{RTEMSTAR}
tar xjf ../archive/@value{RTEMSTAR}
@end example
This creates the directory @value{RTEMSUNTAR}.
@@ -54,11 +51,13 @@ This creates the directory @value{RTEMSUNTAR}.
@section Add <INSTALL_POINT>/bin to Executable PATH
In order to compile RTEMS, you must have the cross compilation toolset
in your search path. The following command appends the directory
where the tools were installed prior to this point:
in your search path. It is important to have the RTEMS toolset first
in your path to ensure that you are using the intended version of all
tools. The following command prepends the directory
where the tools were installed in a previous step:
@example
export PATH=$PATH:<INSTALL_POINT>/bin
export PATH=<INSTALL_POINT>/bin:${PATH}
@end example
NOTE: The above command is in Bourne shell (@code{sh}) syntax and

2
doc/started/sample.t
View File

@@ -210,7 +210,7 @@ applications:
@example
cd tools
tar xzf ../archive/hello_world_ada.tgz
tar xjf ../archive/ada-examples-@value{VERSION}.tar.bz2
@end example
@subheading Create a BSP Specific Makefile