[417fcc73] | 1 | @c |
---|
[6449498] | 2 | @c COPYRIGHT (c) 1988-2002. |
---|
[417fcc73] | 3 | @c On-Line Applications Research Corporation (OAR). |
---|
| 4 | @c All rights reserved. |
---|
| 5 | @c |
---|
| 6 | @c $Id$ |
---|
| 7 | @c |
---|
| 8 | |
---|
[6113b3a] | 9 | @chapter Building the GNU C/C++ Cross Compiler Toolset |
---|
| 10 | |
---|
[6449498] | 11 | NOTE: This chapter does @b{NOT} apply if you installed |
---|
| 12 | prebuilt toolset executables for BINUTILS, GCC, NEWLIB, |
---|
| 13 | and GDB. If you installed prebuilt executables for all |
---|
| 14 | of those, proceed to @ref{Building RTEMS}. If you require |
---|
| 15 | a GDB with a special configuration to connect to your |
---|
| 16 | target board, then proceed to @ref{Building the GNU Debugger GDB} |
---|
| 17 | for some advice. |
---|
| 18 | |
---|
[bdec2709] | 19 | This chapter describes the steps required to acquire the |
---|
| 20 | source code for a GNU cross compiler toolset, apply |
---|
| 21 | any required RTEMS specific patches, compile that |
---|
| 22 | toolset and install it. |
---|
| 23 | |
---|
[9f9efbc] | 24 | It is recommended that when toolset binaries are available for |
---|
| 25 | your particular host, that they be used. Prebuilt binaries |
---|
| 26 | are much easier to install. |
---|
| 27 | |
---|
[6449498] | 28 | @c |
---|
| 29 | @c Building BINUTILS GCC and NEWLIB |
---|
| 30 | @c |
---|
| 31 | @section Building BINUTILS GCC and NEWLIB |
---|
[57a736ff] | 32 | |
---|
[6449498] | 33 | NOTE: This step is NOT required if prebuilt executables for |
---|
| 34 | BINUTILS, GCC, and NEWLIB were installed. |
---|
[0df2ab87] | 35 | |
---|
[6449498] | 36 | This section describes the process of building BINUTILS, GCC, and |
---|
| 37 | NEWLIB using a variety of methods. Included is information on |
---|
| 38 | obtaining the source code and patches, applying patches, and |
---|
| 39 | building and installing the tools using multiple methods. |
---|
[0df2ab87] | 40 | |
---|
[6449498] | 41 | @c |
---|
| 42 | @c Obtain Source and Patches for BINUTILS GCC and NEWLIB |
---|
| 43 | @c |
---|
[0df2ab87] | 44 | |
---|
[6449498] | 45 | @subsection Obtain Source and Patches for BINUTILS GCC and NEWLIB |
---|
[79bb9221] | 46 | |
---|
[6449498] | 47 | NOTE: This step is required for all methods of building BINUTILS, |
---|
| 48 | GCC, and NEWLIB. |
---|
[fffe9266] | 49 | |
---|
[6449498] | 50 | This section lists the components required to build BINUTILS, GCC, |
---|
| 51 | and NEWLIB from source to target RTEMS. These files should be |
---|
| 52 | placed in your @code{archive} directory. Included are the locations |
---|
| 53 | of each component as well as any required RTEMS specific patches. |
---|
[fffe9266] | 54 | |
---|
[6449498] | 55 | @need 1000 |
---|
[bf31efd] | 56 | @subheading @value{GCCUNTAR} |
---|
[fffe9266] | 57 | @example |
---|
[6e8d424] | 58 | FTP Site: @value{GCCFTPSITE} |
---|
| 59 | Directory: @value{GCCFTPDIR} |
---|
| 60 | File: @value{GCCTAR} |
---|
[bf31efd] | 61 | @c @ifset use-html |
---|
| 62 | URL: @uref{ftp://@value{GCCFTPSITE}@value{GCCFTPDIR}/@value{GCCTAR},,ftp://@value{GCCFTPSITE}@value{GCCFTPDIR}/@value{GCCTAR}} |
---|
| 63 | @c URL: ftp://@value{GCCFTPSITE}@value{GCCFTPDIR} |
---|
| 64 | @c @end ifset |
---|
[fffe9266] | 65 | @end example |
---|
| 66 | |
---|
[6449498] | 67 | @need 1000 |
---|
[bf31efd] | 68 | @subheading @value{BINUTILSUNTAR} |
---|
[fffe9266] | 69 | @example |
---|
[6e8d424] | 70 | FTP Site: @value{BINUTILSFTPSITE} |
---|
| 71 | Directory: @value{BINUTILSFTPDIR} |
---|
| 72 | File: @value{BINUTILSTAR} |
---|
[bf31efd] | 73 | @c @ifset use-html |
---|
| 74 | URL: @uref{ftp://@value{BINUTILSFTPSITE}@value{BINUTILSFTPDIR}/@value{BINUTILSTAR},,ftp://@value{BINUTILSFTPSITE}@value{BINUTILSFTPDIR}/@value{BINUTILSTAR}} |
---|
| 75 | @c URL: ftp://@value{BINUTILSFTPSITE}@value{BINUTILSFTPDIR}/@value{BINUTILSTAR} |
---|
| 76 | @c @end ifset |
---|
[fffe9266] | 77 | @end example |
---|
| 78 | |
---|
[6449498] | 79 | @need 1000 |
---|
[bf31efd] | 80 | @subheading @value{NEWLIBUNTAR} |
---|
[fffe9266] | 81 | @example |
---|
[6e8d424] | 82 | FTP Site: @value{NEWLIBFTPSITE} |
---|
| 83 | Directory: @value{NEWLIBFTPDIR} |
---|
| 84 | File: @value{NEWLIBTAR} |
---|
[bf31efd] | 85 | @c @ifset use-html |
---|
| 86 | URL: @uref{ftp://@value{NEWLIBFTPSITE}@value{NEWLIBFTPDIR}/@value{NEWLIBTAR},,ftp://@value{NEWLIBFTPSITE}@value{NEWLIBFTPDIR}/@value{NEWLIBTAR}} |
---|
| 87 | @c URL: ftp://@value{NEWLIBFTPSITE}@value{NEWLIBFTPDIR}/@value{NEWLIBTAR} |
---|
| 88 | @c @end ifset |
---|
[fffe9266] | 89 | @end example |
---|
| 90 | |
---|
[6449498] | 91 | @need 1000 |
---|
[dff0a57c] | 92 | @subheading RTEMS Specific Tool Patches and Scripts |
---|
[fffe9266] | 93 | @example |
---|
[6e8d424] | 94 | FTP Site: @value{RTEMSFTPSITE} |
---|
| 95 | Directory: @value{RTEMSFTPDIR}/c_tools/source |
---|
[bf31efd] | 96 | @ifset BINUTILSPATCHVERSION |
---|
[6e8d424] | 97 | File: @value{BINUTILSRTEMSPATCH} |
---|
[fffe9266] | 98 | @end ifset |
---|
[bf31efd] | 99 | @ifset NEWLIBPATCHVERSION |
---|
[6e8d424] | 100 | File: @value{NEWLIBRTEMSPATCH} |
---|
[fffe9266] | 101 | @end ifset |
---|
[bf31efd] | 102 | @ifset GCCPATCHVERSION |
---|
[6e8d424] | 103 | File: @value{GCCRTEMSPATCH} |
---|
[fffe9266] | 104 | @end ifset |
---|
[dff0a57c] | 105 | @ifset use-html |
---|
[6e8d424] | 106 | @c URL: @uref{ftp://@value{RTEMSFTPSITE}@value{RTEMSFTPDIR}/c_tools/source,Download RTEMS Patches and Scripts} |
---|
| 107 | URL: ftp://@value{RTEMSFTPSITE}@value{RTEMSFTPDIR}/c_tools/source |
---|
[dff0a57c] | 108 | @end ifset |
---|
[fffe9266] | 109 | @end example |
---|
| 110 | |
---|
[6449498] | 111 | @c |
---|
| 112 | @c Unarchiving the Tools |
---|
| 113 | @c |
---|
| 114 | @subsection Unarchiving the Tools |
---|
| 115 | |
---|
| 116 | NOTE: This step is required if building BINUTILS, GCC, and NEWLIB |
---|
[4a675a5c] | 117 | using the procedure described in @ref{Using configure and make}. |
---|
| 118 | It is @b{NOT} required if using the procedure |
---|
[6449498] | 119 | described in @ref{Using RPM to Build BINUTILS GCC and NEWLIB}. |
---|
[0df2ab87] | 120 | |
---|
[b2e3795] | 121 | GNU source distributions are archived using @code{tar} and |
---|
| 122 | compressed using either @code{gzip} or @code{bzip}. |
---|
| 123 | If compressed with @code{gzip}, the extension @code{.gz} is used. |
---|
| 124 | If compressed with @code{bzip}, the extension @code{.bz2} is used. |
---|
| 125 | |
---|
[0df2ab87] | 126 | While in the @code{tools} directory, unpack the compressed |
---|
[b2e3795] | 127 | tar files for BINUTILS, GCC, and NEWLIB using the appropriate |
---|
| 128 | command based upon the compression program used. |
---|
[417fcc73] | 129 | |
---|
| 130 | @example |
---|
| 131 | cd tools |
---|
[b2e3795] | 132 | tar xzf ../archive/TOOLNAME.tar.gz # for gzip'ed tools |
---|
| 133 | tar xIf ../archive/TOOLNAME.tar.bz2 # for bzip'ed tools |
---|
[417fcc73] | 134 | @end example |
---|
| 135 | |
---|
[b2e3795] | 136 | After the compressed tar files have been unpacked using |
---|
| 137 | the appropriate commands, the following |
---|
[6113b3a] | 138 | directories will have been created under tools. |
---|
| 139 | |
---|
| 140 | @itemize @bullet |
---|
[6e8d424] | 141 | @item @value{BINUTILSUNTAR} |
---|
| 142 | @item @value{GCCUNTAR} |
---|
| 143 | @item @value{NEWLIBUNTAR} |
---|
[6113b3a] | 144 | @end itemize |
---|
| 145 | |
---|
[ae2e9f2] | 146 | The tree should look something like the following figure: |
---|
[0df2ab87] | 147 | |
---|
| 148 | @example |
---|
| 149 | @group |
---|
[ae2e9f2] | 150 | /whatever/prefix/you/choose/ |
---|
| 151 | archive/ |
---|
[6e8d424] | 152 | @value{GCCTAR} |
---|
| 153 | @value{BINUTILSTAR} |
---|
| 154 | @value{NEWLIBTAR} |
---|
[bf31efd] | 155 | @ifset GCCPATCHVERSION |
---|
[6e8d424] | 156 | @value{GCCRTEMSPATCH} |
---|
[0df2ab87] | 157 | @end ifset |
---|
[bf31efd] | 158 | @ifset BINUTILSPATCHVERSION |
---|
[6e8d424] | 159 | @value{BINUTILSRTEMSPATCH} |
---|
[ae2e9f2] | 160 | @end ifset |
---|
[bf31efd] | 161 | @ifset NEWLIBPATCHVERSION |
---|
[6e8d424] | 162 | @value{NEWLIBRTEMSPATCH} |
---|
[ae2e9f2] | 163 | @end ifset |
---|
| 164 | tools/ |
---|
[6e8d424] | 165 | @value{BINUTILSUNTAR}/ |
---|
| 166 | @value{GCCUNTAR}/ |
---|
| 167 | @value{NEWLIBUNTAR}/ |
---|
[0df2ab87] | 168 | @end group |
---|
| 169 | @end example |
---|
| 170 | |
---|
[77ea5d30] | 171 | @c |
---|
[6449498] | 172 | @c Applying RTEMS Patches |
---|
[77ea5d30] | 173 | @c |
---|
| 174 | |
---|
[6449498] | 175 | @subsection Applying RTEMS Patches |
---|
[77ea5d30] | 176 | |
---|
[6449498] | 177 | NOTE: This step is required if building BINUTILS, GCC, and NEWLIB |
---|
[4a675a5c] | 178 | using the procedures described in @ref{Using configure and make}. |
---|
| 179 | It is @b{NOT} required if using the procedure |
---|
[6449498] | 180 | described in @ref{Using RPM to Build BINUTILS GCC and NEWLIB}. |
---|
[cdf30aba] | 181 | |
---|
[6449498] | 182 | This section describes the process of applying the RTEMS patches |
---|
| 183 | to GCC, NEWLIB, and BINUTILS. |
---|
[513196f] | 184 | |
---|
[bdec2709] | 185 | @c |
---|
[adee5979] | 186 | @c GCC patches |
---|
[bdec2709] | 187 | @c |
---|
| 188 | |
---|
[6449498] | 189 | @subheading Apply RTEMS Patch to GCC |
---|
[bdec2709] | 190 | |
---|
[bf31efd] | 191 | @ifclear GCCPATCHVERSION |
---|
| 192 | No RTEMS specific patches are required for @value{GCCUNTAR} to |
---|
[6e8d424] | 193 | support @value{RTEMSVERSION}. |
---|
[bdec2709] | 194 | @end ifclear |
---|
| 195 | |
---|
[bf31efd] | 196 | @ifset GCCPATCHVERSION |
---|
[bdec2709] | 197 | |
---|
| 198 | Apply the patch using the following command sequence: |
---|
| 199 | |
---|
| 200 | @example |
---|
[6e8d424] | 201 | cd tools/@value{GCCUNTAR} |
---|
| 202 | cat ../../archive/@value{GCCRTEMSPATCH} | \ |
---|
[6449498] | 203 | patch -p1 |
---|
[bdec2709] | 204 | @end example |
---|
| 205 | |
---|
[9789eefc] | 206 | If the patch was compressed with the @code{gzip} program, it will |
---|
| 207 | have a suffix of @code{.gz} and you should use @code{zcat} instead |
---|
| 208 | of @code{cat} as shown above. If the patch was compressed with |
---|
| 209 | the @code{gzip} program, it will have a suffix of @code{.bz2} and |
---|
| 210 | you should use @code{bzcat} instead of @code{cat} as shown above. |
---|
| 211 | |
---|
[bdec2709] | 212 | Check to see if any of these patches have been rejected using the following |
---|
| 213 | sequence: |
---|
| 214 | |
---|
| 215 | @example |
---|
[6e8d424] | 216 | cd tools/@value{GCCUNTAR} |
---|
[bdec2709] | 217 | find . -name "*.rej" -print |
---|
| 218 | @end example |
---|
| 219 | |
---|
| 220 | If any files are found with the .rej extension, a patch has been rejected. |
---|
[77ea5d30] | 221 | This should not happen with a good patch file which is properly applied. |
---|
[bdec2709] | 222 | |
---|
| 223 | @end ifset |
---|
| 224 | |
---|
| 225 | @c |
---|
| 226 | @c BINUTILS patches |
---|
| 227 | @c |
---|
| 228 | |
---|
[6449498] | 229 | @subheading Apply RTEMS Patch to binutils |
---|
[bdec2709] | 230 | |
---|
[bf31efd] | 231 | @ifclear BINUTILSPATCHVERSION |
---|
| 232 | No RTEMS specific patches are required for @value{BINUTILSUNTAR} to |
---|
[6e8d424] | 233 | support @value{RTEMSVERSION}. |
---|
[bdec2709] | 234 | @end ifclear |
---|
[417fcc73] | 235 | |
---|
[bf31efd] | 236 | @ifset BINUTILSPATCHVERSION |
---|
[bdec2709] | 237 | Apply the patch using the following command sequence: |
---|
[417fcc73] | 238 | |
---|
| 239 | @example |
---|
[6e8d424] | 240 | cd tools/@value{BINUTILSUNTAR} |
---|
| 241 | cat ../../archive/@value{BINUTILSRTEMSPATCH} | \ |
---|
[6449498] | 242 | patch -p1 |
---|
[417fcc73] | 243 | @end example |
---|
| 244 | |
---|
[9789eefc] | 245 | If the patch was compressed with the @code{gzip} program, it will |
---|
| 246 | have a suffix of @code{.gz} and you should use @code{zcat} instead |
---|
| 247 | of @code{cat} as shown above. If the patch was compressed with |
---|
| 248 | the @code{gzip} program, it will have a suffix of @code{.bz2} and |
---|
| 249 | you should use @code{bzcat} instead of @code{cat} as shown above. |
---|
| 250 | |
---|
[6113b3a] | 251 | Check to see if any of these patches have been rejected using the following |
---|
| 252 | sequence: |
---|
| 253 | |
---|
| 254 | @example |
---|
[6e8d424] | 255 | cd tools/@value{BINUTILSUNTAR} |
---|
[6113b3a] | 256 | find . -name "*.rej" -print |
---|
| 257 | @end example |
---|
[417fcc73] | 258 | |
---|
[6113b3a] | 259 | If any files are found with the .rej extension, a patch has been rejected. |
---|
[77ea5d30] | 260 | This should not happen with a good patch file which is properly applied. |
---|
[6113b3a] | 261 | |
---|
[bdec2709] | 262 | @end ifset |
---|
[6113b3a] | 263 | |
---|
[bdec2709] | 264 | @c |
---|
| 265 | @c Newlib patches |
---|
| 266 | @c |
---|
[6113b3a] | 267 | |
---|
[6449498] | 268 | @subheading Apply RTEMS Patch to newlib |
---|
[bdec2709] | 269 | |
---|
[bf31efd] | 270 | @ifclear NEWLIBPATCHVERSION |
---|
| 271 | No RTEMS specific patches are required for @value{NEWLIBUNTAR} to |
---|
[6e8d424] | 272 | support @value{RTEMSVERSION}. |
---|
[bdec2709] | 273 | @end ifclear |
---|
| 274 | |
---|
[bf31efd] | 275 | @ifset NEWLIBPATCHVERSION |
---|
[bdec2709] | 276 | |
---|
| 277 | Apply the patch using the following command sequence: |
---|
[6113b3a] | 278 | |
---|
| 279 | @example |
---|
[6e8d424] | 280 | cd tools/@value{NEWLIBUNTAR} |
---|
| 281 | cat ../../archive/@value{NEWLIBRTEMSPATCH} | \ |
---|
[6449498] | 282 | patch -p1 |
---|
[6113b3a] | 283 | @end example |
---|
| 284 | |
---|
[9789eefc] | 285 | If the patch was compressed with the @code{gzip} program, it will |
---|
| 286 | have a suffix of @code{.gz} and you should use @code{zcat} instead |
---|
| 287 | of @code{cat} as shown above. If the patch was compressed with |
---|
| 288 | the @code{gzip} program, it will have a suffix of @code{.bz2} and |
---|
| 289 | you should use @code{bzcat} instead of @code{cat} as shown above. |
---|
| 290 | |
---|
[6113b3a] | 291 | Check to see if any of these patches have been rejected using the following |
---|
| 292 | sequence: |
---|
| 293 | |
---|
| 294 | @example |
---|
[6e8d424] | 295 | cd tools/@value{NEWLIBUNTAR} |
---|
[6113b3a] | 296 | find . -name "*.rej" -print |
---|
| 297 | @end example |
---|
| 298 | |
---|
| 299 | If any files are found with the .rej extension, a patch has been rejected. |
---|
[77ea5d30] | 300 | This should not happen with a good patch file which is properly applied. |
---|
[6113b3a] | 301 | |
---|
[bdec2709] | 302 | @end ifset |
---|
| 303 | |
---|
[6449498] | 304 | |
---|
| 305 | @c |
---|
| 306 | @c Compiling and Installing BINUTILS GCC and NEWLIB |
---|
| 307 | @c |
---|
| 308 | |
---|
| 309 | @subsection Compiling and Installing BINUTILS GCC and NEWLIB |
---|
| 310 | |
---|
[4a675a5c] | 311 | There are two supported methods to compile and install BINUTILS, GCC, |
---|
| 312 | and NEWLIB: |
---|
[6449498] | 313 | |
---|
| 314 | @itemize @bullet |
---|
| 315 | @item RPM |
---|
| 316 | @item direct invocation of @code{configure} and @code{make} |
---|
| 317 | @end itemize |
---|
| 318 | |
---|
| 319 | Direct invocation of @code{configure} and @code{make} provides more control |
---|
| 320 | and easier recovery from problems when building. |
---|
| 321 | |
---|
| 322 | @c |
---|
| 323 | @c Using RPM to Build BINUTILS GCC and NEWLIB |
---|
| 324 | @c |
---|
| 325 | |
---|
| 326 | @subsubsection Using RPM to Build BINUTILS GCC and NEWLIB |
---|
| 327 | |
---|
| 328 | NOTE: The procedures described in the following sections must |
---|
| 329 | be completed before this step: |
---|
| 330 | |
---|
| 331 | @itemize @bullet |
---|
| 332 | @item @ref{Obtain Source and Patches for BINUTILS GCC and NEWLIB} |
---|
| 333 | @end itemize |
---|
| 334 | |
---|
| 335 | RPM automatically unarchives the source and applies any needed |
---|
| 336 | patches so you do @b{NOT} have to manually perform the procedures |
---|
| 337 | described @ref{Unarchiving the Tools} and |
---|
| 338 | @ref{Applying RTEMS Patches}. |
---|
| 339 | |
---|
| 340 | This section describes the process of building binutils, gcc, and |
---|
| 341 | newlib using RPM. RPM is a packaging format which can be used to |
---|
| 342 | distribute binary files as well as to capture the procedure and |
---|
| 343 | source code used to produce those binary files. Before |
---|
| 344 | attempting to build any RPM from source, it is necessary to |
---|
| 345 | ensure that all required source and patches are in the @code{SOURCES} |
---|
| 346 | directory under the RPM root (probably @code{/usr/src/redhat} or |
---|
| 347 | @code{/usr/local/src/redhat}) on your machine. This procedure |
---|
| 348 | starts by installing the source RPMs as shown in the following |
---|
| 349 | example: |
---|
| 350 | |
---|
| 351 | @example |
---|
[bf31efd] | 352 | rpm -i i386-rtems-binutils-collection-@value{BINUTILSVERSION}-@value{BINUTILSRPMRELEASE}.nosrc.rpm |
---|
| 353 | rpm -i i386-rtems-gcc-newlib-gcc@value{GCCVERSION}newlib@value{NEWLIBVERSION}-@value{GCCRPMRELEASE}.nosrc.rpm |
---|
[6449498] | 354 | @end example |
---|
| 355 | |
---|
[bf31efd] | 356 | The RTEMS tool source RPMS are called "nosrc" to indicate that one or |
---|
[6449498] | 357 | more source files required to produce the RPMs are not present. |
---|
[bf31efd] | 358 | The RTEMS source RPMs typically include all required patches, but do not |
---|
| 359 | include the large @code{.tar.gz} or @code{.tgz} files for |
---|
[6449498] | 360 | each component such as BINUTILS, GCC, or NEWLIB. These are shared |
---|
| 361 | by all RTEMS RPMs regardless of target CPU and there was no reason |
---|
| 362 | to duplicate them. You will have to get the required source |
---|
| 363 | archive files by hand and place them in the @code{SOURCES} directory |
---|
| 364 | before attempting to build. If you forget to do this, RPM is |
---|
| 365 | smart -- it will tell you what is missing. To determine what is |
---|
| 366 | included or referenced by a particular RPM, use a command like the |
---|
| 367 | following: |
---|
| 368 | |
---|
| 369 | @example |
---|
[bf31efd] | 370 | @c Don't use @value{GCC*} below. This is an example |
---|
| 371 | $ rpm -q -l -p i386-rtems-gcc-newlib-gcc3.2.3newlib1.11.0-1.nosrc.rpm |
---|
| 372 | gcc-3.2.3-rtems-20030507a.diff |
---|
| 373 | i386-rtems-gcc-3.2.3-newlib-1.11.0.spec |
---|
| 374 | newlib-1.11.0-rtems-20030507.diff |
---|
[6449498] | 375 | @end example |
---|
| 376 | |
---|
[bf31efd] | 377 | Notice that there are patch files (the @code{.diff} files) and a file |
---|
| 378 | describing the build procedure and files produced (the @code{.spec} file), |
---|
| 379 | but no source archives (the @code{*tar.*} files). |
---|
| 380 | When installing this source RPM |
---|
| 381 | (@code{rpm -U i386-rtems-gcc-newlib-gcc3.2.3newlib1.11.0-1.nosrc.rpm}), |
---|
| 382 | the @code{.spec} file is placed in the @code{SPECS} directory under the RPM root |
---|
| 383 | directory, while the @code{*.diff} files are placed into the @code{SOURCES} |
---|
| 384 | directory. |
---|
[6449498] | 385 | |
---|
| 386 | @c |
---|
| 387 | @c Configuring and Building BINUTILS using RPM |
---|
| 388 | @c |
---|
| 389 | |
---|
| 390 | @subheading Configuring and Building BINUTILS using RPM |
---|
| 391 | |
---|
| 392 | The following example illustrates the invocation of RPM to build a new, |
---|
| 393 | locally compiled, binutils binary RPM that matches the installed source |
---|
| 394 | RPM. This example assumes that all of the required source is installed. |
---|
| 395 | |
---|
| 396 | @example |
---|
| 397 | cd <RPM_ROOT_DIRECTORY>/SPECS |
---|
[bf31efd] | 398 | rpm -bb i386-rtems-binutils-@value{BINUTILSVERSION}.spec |
---|
[6449498] | 399 | @end example |
---|
| 400 | |
---|
| 401 | If the build completes successfully, RPMS like the following will |
---|
| 402 | be generated in a build-host architecture specific subdirectory |
---|
| 403 | of the RPMS directory under the RPM root directory. |
---|
| 404 | |
---|
| 405 | @example |
---|
[bf31efd] | 406 | rtems-base-binutils-@value{BINUTILSVERSION}-@value{BINUTILSRPMRELEASE}.i386.rpm |
---|
| 407 | i386-rtems-binutils-@value{BINUTILSVERSION}-@value{BINUTILSRPMRELEASE}.i386.rpm |
---|
[6449498] | 408 | @end example |
---|
| 409 | |
---|
| 410 | NOTE: It may be necessary to remove the build tree in the |
---|
| 411 | @code{BUILD} directory under the RPM root directory. |
---|
| 412 | |
---|
| 413 | @c |
---|
| 414 | @c Configuring and Building GCC and NEWLIB using RPM |
---|
| 415 | @c |
---|
| 416 | |
---|
| 417 | @subheading Configuring and Building GCC and NEWLIB using RPM |
---|
| 418 | |
---|
| 419 | The following example illustrates the invocation of RPM to build a new, |
---|
| 420 | locally compiled, set of GCC and NEWLIB binary RPMs that match the |
---|
| 421 | installed source RPM. It is also necessary to install the BINUTILS |
---|
| 422 | RPMs and place them in your PATH. This example assumes that all of |
---|
| 423 | the required source is installed. |
---|
| 424 | |
---|
| 425 | @example |
---|
| 426 | cd <RPM_ROOT_DIRECTORY>/RPMS/i386 |
---|
[bf31efd] | 427 | rpm -i rtems-base-binutils-@value{BINUTILSVERSION}-@value{BINUTILSRPMRELEASE}.i386.rpm |
---|
| 428 | rpm -i i386-rtems-binutils-@value{BINUTILSVERSION}-@value{BINUTILSRPMRELEASE}.i386.rpm |
---|
| 429 | export PATH=@value{RTEMSPREFIX}/bin:$PATH |
---|
[6449498] | 430 | cd <RPM_ROOT_DIRECTORY>/SPECS |
---|
[bf31efd] | 431 | rpm -bb i386-rtems-gcc-@value{GCCVERSION}-newlib-@value{NEWLIBVERSION}.spec |
---|
[6449498] | 432 | @end example |
---|
| 433 | |
---|
| 434 | If the build completes successfully, a set of RPMS like the following will |
---|
| 435 | be generated in a build-host architecture specific subdirectory |
---|
| 436 | of the RPMS directory under the RPM root directory. |
---|
| 437 | |
---|
| 438 | @example |
---|
[bf31efd] | 439 | rtems-base-gcc-gcc@value{GCCVERSION}newlib@value{NEWLIBVERSION}-@value{GCCRPMRELEASE}.i386.rpm |
---|
| 440 | rtems-base-chill-gcc@value{GCCVERSION}newlib@value{NEWLIBVERSION}-@value{GCCRPMRELEASE}.i386.rpm |
---|
| 441 | rtems-base-g77-gcc@value{GCCVERSION}newlib@value{NEWLIBVERSION}-@value{GCCRPMRELEASE}.i386.rpm |
---|
| 442 | rtems-base-gcj-gcc@value{GCCVERSION}newlib@value{NEWLIBVERSION}-@value{GCCRPMRELEASE}.i386.rpm |
---|
| 443 | i386-rtems-gcc-gcc@value{GCCVERSION}newlib@value{NEWLIBVERSION}-@value{GCCRPMRELEASE}.i386.rpm |
---|
| 444 | i386-rtems-chill-gcc@value{GCCVERSION}newlib@value{NEWLIBVERSION}-@value{GCCRPMRELEASE}.i386.rpm |
---|
| 445 | i386-rtems-g77-gcc@value{GCCVERSION}newlib@value{NEWLIBVERSION}-@value{GCCRPMRELEASE}.i386.rpm |
---|
| 446 | i386-rtems-gcj-gcc@value{GCCVERSION}newlib@value{NEWLIBVERSION}-@value{GCCRPMRELEASE}.i386.rpm |
---|
| 447 | i386-rtems-objc-gcc@value{GCCVERSION}newlib@value{NEWLIBVERSION}-@value{GCCRPMRELEASE}.i386.rpm |
---|
[6449498] | 448 | @end example |
---|
| 449 | |
---|
| 450 | NOTE: Some targets do not support building all languages. |
---|
| 451 | |
---|
| 452 | NOTE: It may be necessary to remove the build tree in the |
---|
| 453 | @code{BUILD} directory under the RPM root directory. |
---|
| 454 | |
---|
| 455 | @c |
---|
| 456 | @c Using configure and make |
---|
| 457 | @c |
---|
| 458 | |
---|
| 459 | @subsubsection Using configure and make |
---|
| 460 | |
---|
| 461 | NOTE: The procedures described in the following sections must |
---|
| 462 | be completed before this step: |
---|
| 463 | |
---|
| 464 | @itemize @bullet |
---|
| 465 | @item @ref{Obtain Source and Patches for BINUTILS GCC and NEWLIB} |
---|
| 466 | @item @ref{Unarchiving the Tools} |
---|
| 467 | @item @ref{Applying RTEMS Patches} |
---|
| 468 | @end itemize |
---|
| 469 | |
---|
| 470 | This section describes the process of building binutils, gcc, and |
---|
| 471 | newlib manually using @code{configure} and @code{make} directly. |
---|
| 472 | |
---|
| 473 | @c |
---|
| 474 | @c Configuring and Building BINUTILS |
---|
| 475 | @c |
---|
| 476 | |
---|
| 477 | @subheading Configuring and Building BINUTILS |
---|
| 478 | |
---|
| 479 | The following example illustrates the invocation of |
---|
| 480 | @code{configure} and @code{make} |
---|
[6e8d424] | 481 | to build and install @value{BINUTILSUNTAR} for the |
---|
[6449498] | 482 | sparc-rtems target: |
---|
| 483 | |
---|
| 484 | @example |
---|
| 485 | mkdir b-binutils |
---|
| 486 | cd b-binutils |
---|
[6e8d424] | 487 | ../@value{BINUTILSUNTAR}/configure --target=sparc-rtems \ |
---|
[bf31efd] | 488 | --prefix=@value{RTEMSPREFIX} |
---|
[6449498] | 489 | make all |
---|
| 490 | make info |
---|
| 491 | make install |
---|
| 492 | @end example |
---|
| 493 | |
---|
[6e8d424] | 494 | After @value{BINUTILSUNTAR} is built and installed the |
---|
[6449498] | 495 | build directory @code{b-binutils} may be removed. |
---|
| 496 | |
---|
| 497 | For more information on the invocation of @code{configure}, please |
---|
[6e8d424] | 498 | refer to the documentation for @value{BINUTILSUNTAR} or |
---|
| 499 | invoke the @value{BINUTILSUNTAR} @code{configure} command with the |
---|
[6449498] | 500 | @code{--help} option. |
---|
| 501 | |
---|
[3e0c94f] | 502 | NOTE: The shell PATH variable needs to be updated to include the path |
---|
| 503 | the binutils has been installed in. This the prefix used above with |
---|
| 504 | @file{bin} post-fixed. |
---|
| 505 | |
---|
| 506 | @example |
---|
[bf31efd] | 507 | export PATH=$PATH:@value{RTEMSPREFIX}/bin |
---|
[3e0c94f] | 508 | @end example |
---|
| 509 | |
---|
| 510 | Failure to have the binutils in the path will cause the GCC and NEWLIB |
---|
| 511 | build to fail with an error message similar to: |
---|
| 512 | |
---|
| 513 | @example |
---|
| 514 | sparc-rtems-ar: command not found |
---|
| 515 | @end example |
---|
| 516 | |
---|
[6449498] | 517 | @c |
---|
| 518 | @c Configuring and Building GCC and NEWLIB |
---|
| 519 | @c |
---|
| 520 | |
---|
| 521 | @subheading Configuring and Building GCC and NEWLIB |
---|
| 522 | |
---|
[6e8d424] | 523 | Before building @value{GCCUNTAR} and @value{NEWLIBUNTAR}, |
---|
| 524 | @value{BINUTILSUNTAR} must be installed and the directory |
---|
[6449498] | 525 | containing those executables must be in your PATH. |
---|
| 526 | |
---|
| 527 | The C Library is built as a subordinate component of |
---|
[6e8d424] | 528 | @value{GCCUNTAR}. Because of this, the @value{NEWLIBUNTAR} |
---|
| 529 | directory source must be available inside the @value{GCCUNTAR} |
---|
[6449498] | 530 | source tree. This is normally accomplished using a symbolic |
---|
| 531 | link as shown in this example: |
---|
| 532 | |
---|
| 533 | @example |
---|
[6e8d424] | 534 | cd @value{GCCUNTAR} |
---|
| 535 | ln -s ../@value{NEWLIBUNTAR}/newlib . |
---|
[6449498] | 536 | @end example |
---|
| 537 | |
---|
| 538 | The following example illustrates the invocation of |
---|
| 539 | @code{configure} and @code{make} |
---|
[6e8d424] | 540 | to build and install @value{BINUTILSUNTAR} for the |
---|
[6449498] | 541 | sparc-rtems target: |
---|
| 542 | |
---|
| 543 | @example |
---|
| 544 | mkdir b-gcc |
---|
| 545 | cd b-gcc |
---|
[6e8d424] | 546 | ../@value{GCCUNTAR}/configure --target=sparc-rtems \ |
---|
[6449498] | 547 | --with-gnu-as --with-gnu-ld --with-newlib --verbose \ |
---|
[bf31efd] | 548 | --enable-threads --prefix=@value{RTEMSPREFIX} |
---|
[6449498] | 549 | make all |
---|
| 550 | make info |
---|
| 551 | make install |
---|
| 552 | @end example |
---|
| 553 | |
---|
[6e8d424] | 554 | After @value{GCCUNTAR} is built and installed the |
---|
[6449498] | 555 | build directory @code{b-gcc} may be removed. |
---|
| 556 | |
---|
| 557 | For more information on the invocation of @code{configure}, please |
---|
[6e8d424] | 558 | refer to the documentation for @value{GCCUNTAR} or |
---|
| 559 | invoke the @value{GCCUNTAR} @code{configure} command with the |
---|
[6449498] | 560 | @code{--help} option. |
---|
| 561 | |
---|
| 562 | @c |
---|
| 563 | @c Building the GNU Debugger GDB |
---|
| 564 | @c |
---|
| 565 | |
---|
| 566 | @section Building the GNU Debugger GDB |
---|
| 567 | |
---|
| 568 | NOTE: This step is NOT required if prebuilt executables for |
---|
| 569 | the GNU Debugger GDB were installed. |
---|
| 570 | |
---|
| 571 | The GNU Debugger GDB supports many configurations but requires some |
---|
| 572 | means of communicating between the host computer and target board. |
---|
| 573 | This communication can be via a serial port, Ethernet, BDM, or ROM emulator. |
---|
| 574 | The communication protocol can be the GDB remote protocol or GDB |
---|
| 575 | can talk directly to a ROM monitor. This setup is target board |
---|
| 576 | specific. The following configurations have been |
---|
| 577 | successfully used with RTEMS applications: |
---|
| 578 | |
---|
| 579 | @itemize @bullet |
---|
| 580 | @item Sparc Instruction Simulator (SIS) |
---|
| 581 | @item PowerPC Instruction Simulator (PSIM) |
---|
| 582 | @item DINK32 |
---|
| 583 | @item BDM with 68360 and MPC860 CPUs |
---|
| 584 | @item Motorola Mxxxbug found on M68xxx VME boards |
---|
| 585 | @item Motorola PPCbug found on PowerPC VME and CompactPCI boards |
---|
| 586 | @end itemize |
---|
| 587 | |
---|
| 588 | GDB is currently RTEMS thread/task aware only if you are using the |
---|
| 589 | remote debugging support via Ethernet. These are configured |
---|
| 590 | using gdb targets of the form CPU-RTEMS. Note the capital RTEMS. |
---|
| 591 | |
---|
| 592 | It is recommended that when toolset binaries are available for |
---|
| 593 | your particular host, that they be used. Prebuilt binaries |
---|
| 594 | are much easier to install but in the case of gdb may or may |
---|
| 595 | not include support for your particular target board. |
---|
| 596 | |
---|
| 597 | @c |
---|
| 598 | @c Obtain Source and Patches for GDB |
---|
| 599 | @c |
---|
| 600 | |
---|
| 601 | @subsection Obtain Source and Patches for GDB |
---|
| 602 | |
---|
| 603 | NOTE: This step is required for all methods of building GDB. |
---|
| 604 | |
---|
| 605 | This section lists the components required to build GDB |
---|
| 606 | from source to target RTEMS. These files should be |
---|
| 607 | placed in your @code{archive} directory. Included are the locations |
---|
| 608 | of each component as well as any required RTEMS specific patches. |
---|
| 609 | |
---|
| 610 | @need 1000 |
---|
[bf31efd] | 611 | @subheading @value{GDBUNTAR} |
---|
[6449498] | 612 | @example |
---|
[6e8d424] | 613 | FTP Site: @value{GDBFTPSITE} |
---|
| 614 | Directory: @value{GDBFTPDIR} |
---|
| 615 | File: @value{GDBTAR} |
---|
[bf31efd] | 616 | URL: @uref{@value{GDBFTPURL},,@value{GDBFTPURL}} |
---|
[6449498] | 617 | @end example |
---|
| 618 | |
---|
| 619 | @need 1000 |
---|
| 620 | @subheading RTEMS Specific Tool Patches and Scripts |
---|
| 621 | @example |
---|
[6e8d424] | 622 | FTP Site: @value{RTEMSFTPSITE} |
---|
| 623 | Directory: @value{RTEMSFTPDIR}/c_tools/source |
---|
[bf31efd] | 624 | @ifset GDBPATCHVERSION |
---|
[6e8d424] | 625 | File: @value{GDBRTEMSPATCH} |
---|
[bf31efd] | 626 | URL: @uref{ftp://@value{RTEMSFTPSITE}@value{RTEMSFTPDIR}/c_tools/source/@value{GDBRTEMSPATCH},,ftp://@value{RTEMSFTPSITE}@value{RTEMSFTPDIR}/c_tools/source/@value{GDBRTEMSPATCH}} |
---|
[6449498] | 627 | @end ifset |
---|
| 628 | @end example |
---|
| 629 | |
---|
| 630 | @c |
---|
| 631 | @c Unarchiving the GDB Distribution |
---|
| 632 | @c |
---|
| 633 | @subsection Unarchiving the GDB Distribution |
---|
| 634 | |
---|
| 635 | Use the following commands to unarchive the GDB distribution: |
---|
| 636 | |
---|
| 637 | @example |
---|
| 638 | cd tools |
---|
[6e8d424] | 639 | tar xzf ../archive/@value{GDBTAR} |
---|
[6449498] | 640 | @end example |
---|
| 641 | |
---|
[6e8d424] | 642 | The directory @value{GDBUNTAR} is created under the tools directory. |
---|
[6449498] | 643 | |
---|
| 644 | @c |
---|
| 645 | @c Applying RTEMS Patch to GDB |
---|
| 646 | @c |
---|
| 647 | |
---|
| 648 | @subsection Applying RTEMS Patch to GDB |
---|
| 649 | |
---|
[bf31efd] | 650 | @ifclear GDBPATCHVERSION |
---|
[6e8d424] | 651 | No RTEMS specific patches are required for @value{GDBVERSION} to |
---|
| 652 | support @value{RTEMSVERSION}. |
---|
[6449498] | 653 | @end ifclear |
---|
| 654 | |
---|
[bf31efd] | 655 | @ifset GDBPATCHVERSION |
---|
[6449498] | 656 | |
---|
| 657 | Apply the patch using the following command sequence: |
---|
| 658 | |
---|
| 659 | @example |
---|
[6e8d424] | 660 | cd tools/@value{GDBUNTAR} |
---|
| 661 | cat archive/@value{GDBRTEMSPATCH} | \ |
---|
[6449498] | 662 | patch -p1 |
---|
| 663 | @end example |
---|
| 664 | |
---|
[9789eefc] | 665 | If the patch was compressed with the @code{gzip} program, it will |
---|
| 666 | have a suffix of @code{.gz} and you should use @code{zcat} instead |
---|
| 667 | of @code{cat} as shown above. If the patch was compressed with |
---|
| 668 | the @code{gzip} program, it will have a suffix of @code{.bz2} and |
---|
| 669 | you should use @code{bzcat} instead of @code{cat} as shown above. |
---|
| 670 | |
---|
[6449498] | 671 | Check to see if any of these patches have been rejected using the following |
---|
| 672 | sequence: |
---|
| 673 | |
---|
| 674 | @example |
---|
[6e8d424] | 675 | cd tools/@value{GDBUNTAR} |
---|
[6449498] | 676 | find . -name "*.rej" -print |
---|
| 677 | @end example |
---|
| 678 | |
---|
| 679 | If any files are found with the .rej extension, a patch has been rejected. |
---|
| 680 | This should not happen with a good patch file. |
---|
| 681 | |
---|
| 682 | @end ifset |
---|
| 683 | |
---|
| 684 | @c |
---|
| 685 | @c Compiling and Installing the GNU Debugger GDB |
---|
| 686 | @c |
---|
| 687 | |
---|
| 688 | @subsection Compiling and Installing the GNU Debugger GDB |
---|
| 689 | |
---|
| 690 | There are three methods of building the GNU Debugger: |
---|
| 691 | |
---|
| 692 | @itemize @bullet |
---|
| 693 | @item RPM |
---|
| 694 | @item direct invocation of @code{configure} and @code{make} |
---|
| 695 | @end itemize |
---|
| 696 | |
---|
| 697 | Direct invocation of @code{configure} and @code{make} provides more control |
---|
| 698 | and easier recovery from problems when building. |
---|
| 699 | |
---|
| 700 | @c |
---|
| 701 | @c Using RPM to Build GDB |
---|
| 702 | @c |
---|
| 703 | |
---|
| 704 | @subsubsection Using RPM to Build GDB |
---|
| 705 | |
---|
| 706 | This section describes the process of building binutils, gcc, and |
---|
| 707 | newlib using RPM. RPM is a packaging format which can be used to |
---|
| 708 | distribute binary files as well as to capture the procedure and |
---|
| 709 | source code used to produce those binary files. Before |
---|
| 710 | attempting to build any RPM from source, it is necessary to |
---|
| 711 | ensure that all required source and patches are in the @code{SOURCES} |
---|
| 712 | directory under the RPM root (probably @code{/usr/src/redhat} or |
---|
| 713 | @code{/usr/local/src/redhat}) on your machine. This procedure |
---|
| 714 | starts by installing the source RPMs as shown in the following |
---|
| 715 | example: |
---|
| 716 | |
---|
| 717 | @example |
---|
[bf31efd] | 718 | rpm -i i386-rtems-gdb-collection-@value{GDBVERSION}-@value{GDBRPMRELEASE}.nosrc.rpm |
---|
[6449498] | 719 | @end example |
---|
| 720 | |
---|
| 721 | Because RTEMS tool RPMS are called "nosrc" to indicate that one or |
---|
| 722 | more source files required to produce the RPMs are not present. |
---|
| 723 | The RTEMS source GDB RPM does not include the large @code{.tar.gz} or |
---|
| 724 | @code{.tgz} files for GDB. This is shared by all RTEMS RPMs |
---|
| 725 | regardless of target CPU and there was no reason |
---|
| 726 | to duplicate them. You will have to get the required source |
---|
| 727 | archive files by hand and place them in the @code{SOURCES} directory |
---|
| 728 | before attempting to build. If you forget to do this, RPM is |
---|
| 729 | smart -- it will tell you what is missing. To determine what is |
---|
| 730 | included or referenced by a particular RPM, use a command like the |
---|
| 731 | following: |
---|
| 732 | |
---|
| 733 | @example |
---|
[bf31efd] | 734 | $ rpm -q -l -p i386-rtems-gdb-collection-@value{GDBVERSION}-@value{GDBRPMRELEASE}.nosrc.rpm |
---|
| 735 | gdb-@value{GDBVERSION}-rtems-@value{GDBPATCHVERSION}.diff |
---|
| 736 | gdb-@value{GDBVERSION}.tar.gz |
---|
| 737 | i386-rtems-gdb-@value{GDBVERSION}.spec |
---|
[6449498] | 738 | @end example |
---|
| 739 | |
---|
| 740 | Notice that there is a patch file (the @code{.diff} file), a source archive |
---|
| 741 | file (the @code{.tar.gz}), and a file describing the build procedure and |
---|
| 742 | files produced (the @code{.spec} file). The @code{.spec} file is placed |
---|
| 743 | in the @code{SPECS} directory under the RPM root directory. |
---|
| 744 | |
---|
| 745 | @c |
---|
| 746 | @c Configuring and Building GDB using RPM |
---|
| 747 | @c |
---|
| 748 | |
---|
| 749 | @subheading Configuring and Building GDB using RPM |
---|
| 750 | |
---|
| 751 | The following example illustrates the invocation of RPM to build a new, |
---|
| 752 | locally compiled, binutils binary RPM that matches the installed source |
---|
| 753 | RPM. This example assumes that all of the required source is installed. |
---|
| 754 | |
---|
| 755 | @example |
---|
| 756 | cd <RPM_ROOT_DIRECTORY>/SPECS |
---|
[bf31efd] | 757 | rpm -bb i386-rtems-gdb-@value{GDBVERSION}.spec |
---|
[6449498] | 758 | @end example |
---|
| 759 | |
---|
| 760 | If the build completes successfully, RPMS like the following will |
---|
| 761 | be generated in a build-host architecture specific subdirectory |
---|
| 762 | of the RPMS directory under the RPM root directory. |
---|
| 763 | |
---|
| 764 | @example |
---|
[bf31efd] | 765 | rtems-base-gdb-@value{GDBVERSION}-@value{GDBRPMRELEASE}.i386.rpm |
---|
| 766 | i386-rtems-gdb-@value{GDBVERSION}-@value{GDBRPMRELEASE}.i386.rpm |
---|
[6449498] | 767 | @end example |
---|
| 768 | |
---|
| 769 | NOTE: It may be necessary to remove the build tree in the |
---|
| 770 | @code{BUILD} directory under the RPM root directory. |
---|
| 771 | |
---|
| 772 | @c |
---|
| 773 | @c Using the GDB configure Script Directly |
---|
| 774 | @c |
---|
| 775 | |
---|
| 776 | @subsubsection Using the GDB configure Script Directly |
---|
| 777 | |
---|
| 778 | This section describes how to configure the GNU debugger for |
---|
| 779 | RTEMS targets using @code{configure} and @code{make} directly. |
---|
| 780 | The following example illustrates the invocation of @code{configure} |
---|
[6e8d424] | 781 | and @code{make} to build and install @value{GDBUNTAR} for the |
---|
[6449498] | 782 | m68k-rtems target: |
---|
| 783 | |
---|
| 784 | @example |
---|
| 785 | mkdir b-gdb |
---|
| 786 | cd b-gdb |
---|
[6e8d424] | 787 | ../@value{GDBUNTAR}/configure --target=m68k-rtems \ |
---|
[bf31efd] | 788 | --prefix=@value{RTEMSPREFIX} |
---|
[6449498] | 789 | make all |
---|
| 790 | make info |
---|
| 791 | make install |
---|
| 792 | @end example |
---|
| 793 | |
---|
| 794 | For some configurations, it is necessary to specify extra options |
---|
| 795 | to @code{configure} to enable and configure option components |
---|
| 796 | such as a processor simulator. The following is a list of |
---|
| 797 | configurations for which there are extra options: |
---|
| 798 | |
---|
| 799 | @table @b |
---|
| 800 | @item i960-rtems |
---|
| 801 | @code{--enable-sim} |
---|
| 802 | |
---|
| 803 | @item powerpc-rtems |
---|
| 804 | @code{--enable-sim --enable-sim-powerpc --enable-sim-timebase --enable-sim-hardware} |
---|
| 805 | |
---|
| 806 | @item sparc-rtems |
---|
| 807 | @code{--enable-sim} |
---|
| 808 | |
---|
| 809 | @end table |
---|
| 810 | |
---|
[6e8d424] | 811 | After @value{GDBUNTAR} is built and installed the |
---|
[6449498] | 812 | build directory @code{b-gdb} may be removed. |
---|
| 813 | |
---|
| 814 | For more information on the invocation of @code{configure}, please |
---|
[6e8d424] | 815 | refer to the documentation for @value{GDBUNTAR} or |
---|
| 816 | invoke the @value{GDBUNTAR} @code{configure} command with the |
---|
[6449498] | 817 | @code{--help} option. |
---|
| 818 | |
---|
| 819 | @c |
---|
| 820 | @c Common Problems |
---|
| 821 | @c |
---|
| 822 | |
---|
[3048b8f] | 823 | @section Common Problems |
---|
| 824 | |
---|
| 825 | @subsection Error Message Indicates Invalid Option to Assembler |
---|
| 826 | |
---|
| 827 | If a message like this is printed then the new cross compiler |
---|
| 828 | is most likely using the native assembler instead of the cross |
---|
| 829 | assembler or vice-versa (native compiler using new cross assembler). |
---|
| 830 | This can occur for one of the following reasons: |
---|
| 831 | |
---|
| 832 | @itemize @bullet |
---|
| 833 | |
---|
| 834 | @item Binutils Patch Improperly Applied |
---|
| 835 | @item Binutils Not Built |
---|
| 836 | @item Current Directory is in Your PATH |
---|
| 837 | |
---|
| 838 | @end itemize |
---|
| 839 | |
---|
[6449498] | 840 | If you are using binutils 2.9.1 or newer with certain older versions of |
---|
[0ab65474] | 841 | gcc, they do not agree on what the name of the newly |
---|
[3048b8f] | 842 | generated cross assembler is. Older binutils called it @code{as.new} |
---|
| 843 | which became @code{as.new.exe} under Windows. This is not a valid |
---|
| 844 | file name, so @code{as.new} is now called @code{as-new}. By using the latest |
---|
| 845 | released tool versions and RTEMS patches, this problem will be avoided. |
---|
| 846 | |
---|
| 847 | If binutils did not successfully build the cross assembler, then |
---|
| 848 | the new cross gcc (@code{xgcc}) used to build the libraries can not |
---|
| 849 | find it. Make sure the build of the binutils succeeded. |
---|
| 850 | |
---|
| 851 | If you include the current directory in your PATH, then there |
---|
| 852 | is a chance that the native compiler will accidentally use |
---|
| 853 | the new cross assembler instead of the native one. This usually |
---|
| 854 | indicates that "." is before the standard system directories |
---|
| 855 | in your PATH. As a general rule, including "." in your PATH |
---|
| 856 | is a security risk and should be avoided. Remove "." from |
---|
| 857 | your PATH. |
---|
| 858 | |
---|
[6449498] | 859 | NOTE: In some environments, it may be difficult to remove "." |
---|
[adee5979] | 860 | completely from your PATH. In this case, make sure that "." |
---|
| 861 | is after the system directories containing "as" and "ld". |
---|
| 862 | |
---|
[3048b8f] | 863 | @subsection Error Messages Indicating Configuration Problems |
---|
| 864 | |
---|
| 865 | If you see error messages like the following, |
---|
| 866 | |
---|
| 867 | @itemize @bullet |
---|
| 868 | |
---|
[6449498] | 869 | @item cannot configure libiberty |
---|
[3048b8f] | 870 | @item coff-emulation not found |
---|
| 871 | @item etc. |
---|
| 872 | |
---|
| 873 | @end itemize |
---|
| 874 | |
---|
| 875 | Then it is likely that one or more of your gnu tools is |
---|
| 876 | already configured locally in its source tree. You can check |
---|
| 877 | for this by searching for the @code{config.status} file |
---|
| 878 | in the various tool source trees. The following command |
---|
| 879 | does this for the binutils source: |
---|
| 880 | |
---|
| 881 | @example |
---|
[6e8d424] | 882 | find @value{BINUTILSUNTAR} -name config.status -print |
---|
[3048b8f] | 883 | @end example |
---|
| 884 | |
---|
| 885 | The solution for this is to execute the command |
---|
| 886 | @code{make distclean} in each of the GNU tools |
---|
| 887 | root source directory. This should remove all |
---|
| 888 | generated files including Makefiles. |
---|
| 889 | |
---|
| 890 | This situation usually occurs when you have previously |
---|
| 891 | built the tool source for some non-RTEMS target. The |
---|
| 892 | generated configuration specific files are still in |
---|
| 893 | the source tree and the include path specified during |
---|
| 894 | the RTEMS build accidentally picks up the previous |
---|
| 895 | configuration. The include path used is something like |
---|
| 896 | this: |
---|
| 897 | |
---|
| 898 | @example |
---|
[6e8d424] | 899 | -I../../@value{BINUTILSUNTAR}/gcc -I/@value{BINUTILSUNTAR}/gcc/include -I. |
---|
[3048b8f] | 900 | @end example |
---|
| 901 | |
---|
| 902 | Note that the tool source directory is searched before the |
---|
| 903 | build directory. |
---|
| 904 | |
---|
| 905 | This situation can be avoided entirely by never using |
---|
| 906 | the source tree as the build directory -- even for |
---|
[6449498] | 907 | |
---|