1 | @c |
---|
2 | @c COPYRIGHT (c) 1988-1998. |
---|
3 | @c On-Line Applications Research Corporation (OAR). |
---|
4 | @c All rights reserved. |
---|
5 | @c |
---|
6 | @c $Id$ |
---|
7 | @c |
---|
8 | |
---|
9 | @chapter Requirements |
---|
10 | |
---|
11 | A fairly large amount of disk space is required to perform the build of the |
---|
12 | GNU C/C++ Cross Compiler Tools for RTEMS. The following table may help in |
---|
13 | assessing the amount of disk space required for your installation: |
---|
14 | |
---|
15 | @example |
---|
16 | +------------------------------------+--------------------------+ |
---|
17 | | Component | Disk Space Required | |
---|
18 | +------------------------------------+--------------------------+ |
---|
19 | | archive directory | 30 Mbytes | |
---|
20 | | tools src unzipped | 100 Mbytes | |
---|
21 | | each individual build directory | 300 Mbytes worst case | |
---|
22 | | each installation directory | 20-130 Mbytes | |
---|
23 | +------------------------------------+--------------------------+ |
---|
24 | @end example |
---|
25 | |
---|
26 | The disk space required for each installation directory depends |
---|
27 | primarily on the number of RTEMS BSPs which are to be installed. |
---|
28 | If a single BSP is installed, then the size of each install directory |
---|
29 | will tend to be in the 40-60 Mbyte range. |
---|
30 | |
---|
31 | The instructions in this manual should work on any computer running |
---|
32 | a UNIX variant. Some native GNU tools are used by this procedure |
---|
33 | including: |
---|
34 | |
---|
35 | @itemize @bullet |
---|
36 | @item GCC |
---|
37 | @item GNAT |
---|
38 | @item GNU make |
---|
39 | @end itemize |
---|
40 | |
---|
41 | In addition, some native utilities may be deficient for building |
---|
42 | the GNU tools. |
---|
43 | |
---|
44 | @section Native GNAT |
---|
45 | |
---|
46 | The native GNAT must be installed in the default location or built |
---|
47 | from source. No GCC or GNAT environment variables should be set during |
---|
48 | the build or use of the cross GNAT/RTEMS toolset as this could result in |
---|
49 | an unpredictable mix of native and cross toolsets. |
---|
50 | |
---|
51 | Binaries for native GNAT installations are available at the primary |
---|
52 | GNAT ftp site (@value{GNAT-FTP}. Installation instructions are |
---|
53 | included with the binary GNAT distributions. The binary installation |
---|
54 | should be installed in the default location or installed in a |
---|
55 | non-default location and used ONLY to build a native GNAT from source. |
---|
56 | This final native GNAT will be used to build the GNAT/RTEMS cross |
---|
57 | development toolset. |
---|
58 | |
---|
59 | @subsection Verifying Correct Operation of Native GNAT |
---|
60 | |
---|
61 | It is imperative that the native GNAT installation work correctly for |
---|
62 | the installation of GNAT/RTEMS to succeed. It is recommended that the |
---|
63 | user verify that the native GNAT is installed correctly by performing |
---|
64 | these tests: |
---|
65 | |
---|
66 | @subsubsection Native Hello World Test |
---|
67 | |
---|
68 | Place the following Ada source code in hello.adb: |
---|
69 | |
---|
70 | @example |
---|
71 | with Text_IO; use Text_IO; |
---|
72 | |
---|
73 | procedure Hello is |
---|
74 | begin |
---|
75 | Put_Line ( "Hello World"); |
---|
76 | end Hello; |
---|
77 | @end example |
---|
78 | |
---|
79 | Use the following command sequence to ompile and execute the above program: |
---|
80 | |
---|
81 | @example |
---|
82 | gnatmake hello |
---|
83 | ./hello |
---|
84 | @end example |
---|
85 | |
---|
86 | If the message @code{Hello World} is printed, then the native installation |
---|
87 | of GNAT operates well enough to proceed. |
---|
88 | |
---|
89 | @subsubsection Insure GCC and GNAT Environment Variables Are Not Set |
---|
90 | |
---|
91 | If any of the following commands produce output, then you have |
---|
92 | environment variables overriding the default behavior of the |
---|
93 | native GNAT toolset. These variables will conflict with the cross |
---|
94 | toolset. Please resolve this problem before proceeding further. |
---|
95 | |
---|
96 | @example |
---|
97 | echo $GCC_EXEC_PREFIX |
---|
98 | echo $ADA_INCLUDE_PATH |
---|
99 | echo $ADA_OBJECTS_PATH |
---|
100 | echo $LD_RUN_PATH |
---|
101 | echo $C_INCLUDE_PATH |
---|
102 | @end example |
---|