diff options
authorRalf Corsepius <>2010-09-27 04:12:24 +0000
committerRalf Corsepius <>2010-09-27 04:12:24 +0000
commit7b3153426cbfb886dc1f834defb87b1d77f387ef (patch)
parenta3bb1addc122f121b5dbfde255ffa8accda7c675 (diff)
2010-09-27 Ralf Corsépius <>
* README.configure: Further cleanup.
2 files changed, 6 insertions, 26 deletions
diff --git a/ChangeLog b/ChangeLog
index 08e76bac69..bc854b1ce7 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,7 @@
+2010-09-27 Ralf Corsépius <>
+ * README.configure: Further cleanup.
2010-09-26 Ralf Corsépius <>
* README.configure: Remove the most obsolete parts.
diff --git a/README.configure b/README.configure
index 34a3342a38..546d99c9e1 100644
--- a/README.configure
+++ b/README.configure
@@ -11,13 +11,11 @@ tools in the Cygnus one-tree structure. Using autoconf also means
that RTEMS now can be built in a separate build directory.
To re-generate auto*tool generated files (configure, etc),
-autoconf-2.59 and automake-1.8 are required.
+autoconf-2.68 and automake-1.11.1 are required.
2. Installation
-2.1 Standalone build
To configure RTEMS for a specific target, run configure in the build
directory. In addition to the standard configure options, the following
RTEMS-specific option are supported:
@@ -82,8 +80,6 @@ within a target architecture. Remember that the target specifies the
CPU family while the BSP specifies the precise board you will be using.
The following targets are supported:
- (none) will build the host-based version on Linux, Solaris and HPUX.
@@ -109,7 +105,7 @@ Installation is done under $(prefix)/rtems.
As an example, to build and install the mvme136 and mvme162 bsps for m68k do:
- (path_to_rtems_src)/configure --target=m68k-rtems
+ (path_to_rtems_src)/configure --target=m68k-rtems4.11
make RTEMS_BSP="mvme136 mvme162"
@@ -121,19 +117,6 @@ test suite.
Documentation is built separately from the source code.
-2.2 Target Dependent Notes
-1. See the README in the bare bsp source directory. This should
- contain all info you need.
-2. The bare bsp source contains a script to show how to build it.
-3. The configure flags must be used to get the bare bsp to work.
- The --enable-bare-cpu-model and --enable-bare-cpu-cflags are the
- only pieces of information. The module is usually a gcc module
- such as m68302 or mcpu32. The flags are passed directly to gcc.
- Use "" if more than one option is specified.
3. To use the installed RTEMS library
@@ -231,13 +214,6 @@ Please refer to the BSP and Device Driver Guide.
All gnu-based bsps have been built on Linux.
-The native (posix) ports have been built and run only on Linux.
-The following configurations have NOT been tested:
- + Anything on Nextstep, HPUX and Irix.
- + The C4x and OR32 ports (requires specially patched toolchain)
8. Prerequisites