Changeset 537449c in rtems


Ignore:
Timestamp:
Jan 22, 2003, 1:47:32 PM (17 years ago)
Author:
Ralf Corsepius <ralf.corsepius@…>
Branches:
4.10, 4.11, 4.8, 4.9, master
Children:
62b24fe
Parents:
8a86d78
Message:

2003-01-22 Ralf Corsepius <corsepiu@…>

  • build45.t: Several fixes and additions.
Location:
doc/FAQ
Files:
2 edited

Legend:

Unmodified
Added
Removed
  • doc/FAQ/ChangeLog

    r8a86d78 r537449c  
     12003-01-22      Ralf Corsepius <corsepiu@faw.uni-ulm.de>
     2
     3        * build45.t: Several fixes and additions.
     4
    152003-01-22      Ralf Corsepius <corsepiu@faw.uni-ulm.de>
    26
  • doc/FAQ/build45.t

    r8a86d78 r537449c  
    5858@subsection Do I need gcc-2.9x for cross compilation?
    5959
     60[FIXME: Partially obsolete]
     61
    6062Not necessarily, but gcc-2.9x is highly recommended, because most development
    6163has taken place using gcc-2.9x and previous versions of gcc are not actively
    6264supported in RTEMS anymore (@ref{Can I use a non-gcc cross-toolchain?}).
    6365
    64 @subsection Where to get autoconf automake ld gcc etc.  ?
     66@subsection Where to get autoconf automake ld gcc etc.?
    6567
    6668The sources of all gnutools are available at any
    67 @uref{GNU,ftp://ftp.gnu.org} mirror.
     69@uref{ftp://ftp.gnu.org,GNU} mirror.
    6870Native Linux binaries should come with any Linux distribution.
    6971Native Cygwin binaries should be available at Cygnus.
     
    7173GNU-Toolchain binaries (gcc, binutils etc.) for Linux and patches required
    7274to build them from source are available from
    73 @uref{OAR Corporation,ftp://ftp.oarcorp.com}.
     75@uref{ftp://ftp.oarcorp.com,OAR Corporation}.
    7476
    7577
     
    9092@end example
    9193
     94@subsection When running bootstrap weird thing start to happen
     95
     96Many possibile causes: Most likely one of these:
     97@itemize @bullet
     98@item You are trying to build RTEMS with insufficient or incompatible
     99versions of autoconf and automake.
     100@item The autotools can't be found because your $PATH might not be set up
     101correctly (Cf. @ref{How to set up $PATH?})
     102@item You have used configure-script options which interfer with RTEMS
     103configuration (Cf. @ref{configure --program-[prefix|suffix|transform-name]})
     104@item You have tripped over a bug in RTEMS ;)
     105@end itemize
     106
     107@subsection configure xxx cannot create executables
     108
     109While running a configure script, you see a message like this:
     110@example
     111checking for m68k-rtems-gcc... (cached) m68k-rtems-gcc
     112checking for C compiler default output... configure: error: C compiler cannot create executables
     113configure: error: /bin/sh '../../../../rtems-ss-@value{VERSION}/c/make/configure'
     114failed for c/make
     115@end example
     116This kind of error message typically indicates a broken toolchain, broken
     117toolchain installation or broken user environment.
     118
     119Examinating the @code{config.long} corresponding to the the failing
     120configure script should provide further information of what
     121actually goes wrong (In the example above: @code{<target>/c/<BSP>/make/config.log})
     122
    92123@subsection Why can I not build RTEMS inside of the source tree?
    93 
    94124
    95125The build-directory hierarchy is setup dynamically at configuration time.
     
    131161
    132162RTEMS >= 4.6.0 configuration is prepared for building RTEMS Canadian Cross,
    133 however building RTEMS Canadian Cross is known to be in it's infancy, so
     163however building RTEMS Canadian Cross is known to be in its infancy, so
    134164your mileage may vary (See @code{README.cdn-X} in the toplevel directory of
    135165RTEMS's source tree for details.)
     
    152182@subsection make debug_install / make profile_install
    153183
     184[FIXME:Partially obsolete]
     185
    154186These make targets are not supported anymore.  Instead, use:
    155187
     
    160192
    161193@subsection make debug / make profile
     194
     195[FIXME:Partially obsolete]
    162196
    163197These make targets are not supported anymore.
     
    185219
    186220@subsection Editing auto* generated files
    187 
    188221
    189222RTEMS uses automake, therefore @b{never}, @b{ever}, @b{ever}
     
    232265@subsection How to merge pre-RTEMS-4.5.0 BSPs into RTEMS-4.5.0?
    233266
    234 The simple answer is that between 4.0 and now, RTEMS has moved to automake
     267[FIXME:Partially obsolete]
     268
     269The simple answer is that between 4.0 and 4.5.0, RTEMS has moved to automake
    235270and greater compliance with GNU conventions.
    236271In 4.0, there was a single configure script at the top of the tree.
    237272Now RTEMS is configured more like other GNU tools -- as a collection of
    238273configurable entities.
    239  
    240274
    241275Each BSP now has its own configure script.
     
    264298It is also known to work in individual cases, but your mileage may vary.
    265299
     300@subsection What is the cpukit?
     301
     302[FIXME:To be extended]
     303
     304One major change having been introduced to RTEMS-4.6.0 is the cpukit,
     305located below the directory @code{cpukit/} in RTEMS's toplevel directory.
     306
    266307@subsection Multilib vs.  RTEMS CPU-variants
    267308
     
    352393and underlying tools installed (Cf. @ref{Required Tools}).
    353394
     395@subsection configure --program-[prefix|suffix|transform-name]
     396
     397These are generic configure script options automatically added by autoconf.
     398RTEMS configuration does not support these, worse, they interfer with
     399RTEMS's configuration -- i.e. @b{do not use them}.
     400
    354401@subsection configure.ac vs. configure.in
    355402
     
    359406RTEMS > 4.5.0 applies autoconf >= 2.50, therefore all former RTEMS's
    360407@code{configure.in}'s have been renamed into @code{configure.ac} and
    361 adapted to autoconf >= 2.50 demands.
     408have been adapted to autoconf >= 2.50 demands.
     409
     410@subsection Reporting bugs
     411
     412Several possibilities (In decreasing preference):
     413@itemize @bullet
     414@item File a bug report at @uref{http://www.oarcorp.com/cgi-bin/gnatweb.pl,OAR's GNAT}
     415@item Send an email to @uref{mailto:rtems-bugs@@OARcorp.com,rtems-bugs@@OARcorp.com}
     416@item Report your problem to one of the RTEMS mailing lists
     417(Cf. @ref{Are there any mailing lists?}).
     418@end itemize
Note: See TracChangeset for help on using the changeset viewer.