source: rtems/doc/started/binaries.t @ bf31efd

4.104.114.84.95
Last change on this file since bf31efd was bf31efd, checked in by Joel Sherrill <joel.sherrill@…>, on Sep 19, 2003 at 6:03:32 PM

2003-09-19 Joel Sherrill <joel@…>

  • .cvsignore, binaries.t, buildc.t, buildrt.t, intro.t, nextstep.t, nt.t, started.texi: Merge from branch.
  • tversions.texi.in: New file.
  • Property mode set to 100644
File size: 5.1 KB
Line 
1@c
2@c  COPYRIGHT (c) 1988-2002.
3@c  On-Line Applications Research Corporation (OAR).
4@c  All rights reserved.
5@c
6@c  $Id$
7@c
8
9@chapter Prebuilt Toolset Executables
10
11Precompiled toolsets are available for Linux, Cygwin, FreeBSD,
12and Solaris.  These are packaged in the following formats:
13
14@itemize @bullet
15@item Linux - RPM
16@item Cygwin - tar.bz2
17@item Solaris - tar.bz2
18@end itemize
19
20RPM is an acronym for the RPM Package Manager.  RPM is the
21native package installer for many Linux distributions including
22RedHat and SuSE.
23@c RPM supports other operating systems including
24@c Cygwin.  @uref{mailto:D.J@@fiddes.surfaid.org,David Fiddes <D.J@@fiddes.surfaid.org>}
25@c did the initial groundwork that lead to Cygwin RPMs being available.
26
27The prebuilt binaries are intended to be easy to install and
28the instructions are similar regardless of the host environment. 
29There are a few structural issues with the packaging of the RTEMS
30Cross Toolset binaries that you need to be aware of.
31
32@enumerate
33@item There are dependencies between the various packages.
34This requires that certain packages be installed before others may be.
35Some packaging formats enforce this dependency.
36
37@item Some packages are target CPU family independent and shared
38across all target architectures.   These are referred to as
39"base" packages.
40
41@item If buildable for a particular CPU, RPMs are provided for
42Ada (gnat), Chill, Java (gcj), Fortran (g77), and Objective-C (objc).
43These binaries are strictly optional.
44
45@end enumerate
46
47NOTE: Installing toolset binaries does not install RTEMS itself, only the tools
48required to build RTEMS.  See @ref{Building RTEMS} for the next
49step in the process.
50
51@section RPMs
52
53This section provides information on installing and removing RPMs.
54
55@subsection Installing RPMs
56
57The following is a sample session illustrating the installation
58of a C/C++ toolset targeting the SPARC architecture. 
59
60@example
61rpm -i rtems-base-binutils-@value{BINUTILSVERSION}-@value{BINUTILSRPMRELEASE}.i386.rpm
62rpm -i sparc-rtems-binutils-@value{BINUTILSVERSION}-@value{BINUTILSRPMRELEASE}.i386.rpm
63rpm -i rtems-base-gcc-gcc@value{GCCVERSION}newlib@value{NEWLIBVERSION}-@value{GCCRPMRELEASE}.i386.rpm
64rpm -i sparc-rtems-gcc-gcc@value{GCCVERSION}newlib@value{NEWLIBVERSION}-@value{GCCRPMRELEASE}.i386.rpm
65rpm -i rtems-base-gdb-@value{GDBVERSION}-@value{GDBRPMRELEASE}.i386.rpm
66rpm -i sparc-rtems-gdb-@value{GDBVERSION}-@value{GDBRPMRELEASE}.i386.rpm
67@end example
68
69Upon successful completion of the above command sequence, a
70C/C++ cross development toolset targeting the SPARC is
71installed in @code{@value{RTEMSPREFIX}}.  In order to use this toolset,
72the directory @code{@value{RTEMSPREFIX}/bin} must be included in your
73PATH.
74
75Once you have successfully installed the RPMs for BINUTILS, GCC,
76NEWLIB, and GDB, then you may proceed directly to @ref{Building RTEMS}. 
77
78@subsection Determining Which RTEMS RPMs are Installed
79
80The following command will report which RTEMS RPMs are currently
81installed:
82
83@example
84rpm -q -g rtems
85@end example
86
87@subsection Removing RPMs
88
89The following is a sample session illustrating the removal
90of a C/C++ toolset targeting the SPARC architecture.
91
92@example
93rpm -e sparc-rtems-gdb-@value{GDBVERSION}-@value{GDBRPMRELEASE}.i386.rpm
94rpm -e rtems-base-gdb-@value{GDBVERSION}-@value{GDBRPMRELEASE}.i386.rpm
95rpm -e sparc-rtems-gcc-gcc@value{GCCVERSION}newlib@value{NEWLIBVERSION}-@value{GCCRPMRELEASE}.i386.rpm
96rpm -e rtems-base-gcc-gcc@value{GCCVERSION}newlib@value{NEWLIBVERSION}-@value{GCCRPMRELEASE}.i386.rpm
97rpm -e sparc-rtems-binutils-@value{BINUTILSVERSION}-@value{BINUTILSRPMRELEASE}.i386.rpm
98rpm -e rtems-base-binutils-@value{BINUTILSVERSION}-@value{BINUTILSRPMRELEASE}.i386.rpm
99@end example
100
101NOTE:  If you have installed any RTEMS BSPs, then it is likely that
102RPM will complain about not being able to remove everything.
103
104@section Zipped Tar Files
105
106This section provides information on installing and removing
107Zipped Tar Files (.tgz).
108
109@subsection Installing Zipped Tar Files
110
111The following is a sample session illustrating the installation
112of a C/C++ toolset targeting the SPARC architecture assuming
113that GNU tar is installed as @code{tar}:
114
115@example
116cd /
117tar xzf rtems-base-binutils-@value{BINUTILSVERSION}-@value{BINUTILSRPMRELEASE}.tgz
118tar xzf sparc-rtems-binutils-@value{BINUTILSVERSION}-@value{BINUTILSRPMRELEASE}.tgz
119tar xzf rtems-base-gcc-gcc@value{GCCVERSION}newlib@value{NEWLIBVERSION}-@value{GCCRPMRELEASE}.tgz
120tar xzf sparc-rtems-gcc-gcc@value{GCCVERSION}newlib@value{NEWLIBVERSION}-@value{GCCRPMRELEASE}.tgz
121tar xzf rtems-base-gdb-@value{GDBVERSION}-@value{GDBRPMRELEASE}.tgz
122tar xzf sparc-rtems-gdb-@value{GDBVERSION}-@value{GDBRPMRELEASE}.tgz
123@end example
124
125Upon successful completion of the above command sequence, a
126C/C++ cross development toolset targeting the SPARC is
127installed in @code{@value{RTEMSPREFIX}}.  In order to use this toolset,
128the directory @code{@value{RTEMSPREFIX}} must be included in your
129PATH.
130
131@subsection Removing Zipped Tar Files
132
133There is no automatic way to remove the contents of a @code{tgz} once
134it is installed.  The contents of the directory @code{@value{RTEMSPREFIX}}
135can be removed but this will likely result in other packages
136being removed as well.
137
138
Note: See TracBrowser for help on using the repository browser.