path: root/README.configure (unfollow)
Commit message (Collapse)AuthorFilesLines
2002-01-202002-01-19 Ralf Corsepius <>Joel Sherrill1-5/+8
* Add --enable-docs support. Add RTEMS_HOST_CONFIG_SUBDIRS(doc). Remove doc/Makefile. * Add HOST_SUBDIRS to SUBDIRS. Remove doc from hard-coded SUBDIRS. * README.configure: Added a bit of information on this new option.
2001-11-082001-11-08 Dennis Ehlin (ECS) <>Joel Sherrill1-1/+1
This modification is part of the submitted modifications necessary to support the IBM PPC405 family. This submission was reviewed by Thomas Doerfler <> who ensured it did not negatively impact the ppc403 BSPs. The submission and tracking process was captured as PR50. * README.configure: Added gen405 BSP.
2001-05-252001-05-25 Joel Sherrill <>Joel Sherrill1-2/+8
* README.configure: Corrected the name of the MRM332 BSP. Strengthened the distinction between what the target and the BSP each select. Added more targets to list.
2001-05-252001-05-25 Joel Sherrill <>Joel Sherrill1-5/+14
* README.configure: Updated the list of BSPs.
2000-11-132000-11-13 Jiri Gaisler <>Joel Sherrill1-1/+1
* README.configure, aclocal/bsp-alias.m4, aclocal/check-bsps.m4: Modified to reflect addition of LEON BSPs as well as the no-FP ERC32 variant.
2000-09-012000-08-31 Ralf Corsepius <>Joel Sherrill1-12/+12
* LICENSE.NET, README, README.configure: Spelling corrections.
2000-02-08Updated.Joel Sherrill1-5/+20
1999-10-05Removed targets and configurations that are no longer functionalJoel Sherrill1-28/+0
and not likely to become so. Comments on each configuration are below. + Force CPU386 - This BSP was developed as part of the initial port of RTEMS to the i386. This board has been unavailable for a long time now. + GO32 - This BSP and some CPU code supported djgpp v1.x. This version is now quite old. No one has stepped forward to update the code to v2.x which may be technically impossible anyway. More importantly, go32 has been superceded by the pc386 BSP.
1999-10-05Removed targets and configurations that are no longer functionalJoel Sherrill1-2/+1
and not likely to become so. Comments on each configuration are below. + Force CPU386 - This BSP was developed as part of the initial port of RTEMS to the i386. This board has been unavailable for a long time now. + GO32 - This BSP and some CPU code supported djgpp v1.x. This version is now quite old. No one has stepped forward to update the code to v2.x which may be technically impossible anyway. More importantly, go32 has been superceded by the pc386 BSP.
1999-04-16Patch from Ralf Corsepius <>:Joel Sherrill1-1/+0
FYI: I am not talking about using "make -C <dir>", which probably is much faster on M$ hosts than RTEMS's implementation, but about removing --enable-gmake-print support and to apply a variant of automake's subdirectory. Automake's subdirectory rule seems to be a little bit faster, but I wouldn't bet on this. Attached to this mail is my proposal. After applying the patch, please run cvs rm aclocal/enable-gmake-print.m4 ./autogen
1999-03-17Patch from Emmanuel Raguet <> to add informationJoel Sherrill1-0/+6
about the enable rdbg configure option.
1999-02-25Corrected the comments on --enable-gcc28 and switched the sense of theJoel Sherrill1-10/+10
--enable-tests switch.
1998-10-13Added missing BSPs.Joel Sherrill1-4/+5
1998-08-20Updated to reflect stack transition.Joel Sherrill1-3/+4
1998-06-27Bare BSP patch from Chris Johns <>. He alsoJoel Sherrill1-2/+16
sent an example bare bsp but we have not decided how to integrate it yet.
1998-03-24Rename hppa1_1 to hppa1.1 and switched to using __XXX__ macros forJoel Sherrill1-2/+2
the CPU family name constants.
1998-02-17Patch from Ralf Corsepius <>:Joel Sherrill1-2/+2
Yep, I have a bunch of bug-fixes and additions pending (Yet another monster patch, ... I can hear you scream :-). 1) : one AC_CONFIG_HEADER(...) line too much. 2) gcc28 support is enabled by default, i.e. if no --enable-gcc28 option is passed on the command line. I am not sure if this is intentional. IMO, AC_ARG_ENABLE for --enable-gcc28 should look like: AC_ARG_ENABLE(gcc28, \ [ --enable-gcc28 enable use of gcc 2.8.x features], \ [case "${enableval}" in yes) RTEMS_USE_GCC272=no ;; no) RTEMS_USE_GCC272=yes ;; *) AC_MSG_ERROR(bad value ${enableval} for gcc-28 option) ;; esac],[RTEMS_USE_GCC272=yes]) 3) At the end of c/src/exec/score/cpu/m68k/m68k.h > #ifdef __cplusplus > } > #endif > > #endif /* !ASM */ in my opinion these two statements should be swapped: > #endif /* !ASM */ > > #ifdef __cplusplus > } > #endif I didn't try to compile for m68k, but does't this give an error? Is it compensated somewhere else - or didn't I look carefully enough? 5) --enable-cpp should probably be renamed to --enable-cxx, as gnu-programs use "cxx" to specify C++ specific configure options, while cpp is used for the preprocessor (e.g egcs uses --with-cxx-includedir, autoconf internally uses $CXX), 6) The macro files from aclocal/*.m4 contain the buggy sed-rules formerly contained in aclocal..m4, i.e. the sed/sort-bug fix to aclocal.m4 didn't make it to aclocal/*.m4. I think I should feel guilty for that - Obviously I submitted the contents of an old aclocal-directory last time. - Sorry. 7) For sh-rtems, we currently need to add additional managers to MANAGERS_REQUIRED (from inside of custom/*.cfg). Currently MANAGERS_REQUIRED is defined in make/compilers/*.cfg. This seems to prevent overriding MANAGERS_REQUIRED from custom/*.cfg files - Obviously the files are included in such a way that the settings from compilers/*cfg always override settings from custom/*.cfg files. Furthermore, I think, defining MANAGERS_* inside gcc-<target>.cfg files is not correct - MANAGERS are not gcc-variant-dependent, but depend on targets/bsps and therefore should be defined in a bsp/target dependent file, e.g. in custom/*.cfg or I think defining default settings for MANAGERS* in custom/default.cfg could be an appropriate location. But this requires all custom/*.cfg files to include default.cfg, which *-posix.cfg files don't seem to do. Therefore I would like propose to move MANAGERS* to - they are included by all custom/*.cfg files. Perhaps we/you should use this opportunity to merge parts from custom/default.cfg into This ensures to have the setting included once per target makefile and will open the opportunity to have autoconf doing additional work on bsp-configurations. Peanuts sofar, ... but here it comes ... (:-) 8) I am preparing a major enhancement to autoconf support for gnutools/compilers. It is not yet finished, but usable and I'll therefore attach a preliminary version to this mail. Motivation: * Fix problems with --enable-gcc28, if target-cc is not gcc28 compatible * Fix -pipe problems * Fix problems with hard-coded paths in configuration files (esp. posix) * Fix consistency problems with explictly given gnutools and gcc's gnutools Currently included: * detection and checking of host and target compiler (gcc/g++) * checking if target gnutools are in path * checking if <target>-gcc -specs works (autodisabling gcc28 if not) * checking if <target>-gcc -pipe works Todo : * *posix.cfg files are not yet adapted => The hard-coded paths for these systems are still in use. * Check if the host compiler $CC is properly propagated to the Makefiles (I doubt it, but this should not matter) * Check if rtems' generic tools still work properly (It looks like, but who knows) * Integrate CXX support into default.cfg or gcc-target-default.cfg (It looks like C++ support is only used by posix BSPs) * Automatically handle RANLIB/MKLIB for targets * Plenty ... (:-) Open problems: * Untested for non-gcc compatible host and target compilers. This should be no problem if the tools are named follow gnutool's naming convention and are included in $PATH while running configure. * Intentionally using different tools than that gcc has been configured for, e.g. use a different assembler ? This should be still possible if XX_FOR_TARGET is hard-coded into custom/*.cfg. I don't see why anybody should want to do this, but who knows? I have tested this version on linux and solaris hosts, with gcc's directories mounted at weird non-standard mount points, using egcs (linux/sh-rtemscoff), gcc- using native tools (solaris), gcc- w/ gnutools (solaris/linux). I don't expect it to break anything, but of cause I can't promise it. It will break most/all *-posix.cfg configuration almost for certain, but not more as rtems' current *posix.cfg configurations already do (hard-coded configurations). I am not sure if this is ready to be included into the next snapshot or not. Perhaps you might try this on your systems and if it you don't notice serious bugs you might put it into the snapshot for public testing (I don't like this, but I don't see another possiblity to test generality). I enclose a patch for and some configuration files which comprizes fixes for all items mentioned except of #3 . Don't forget to run "aclocal -I aclocal; autoconf;" after applying the patch (:-).
1998-02-10Robin Kirkham reported that the install point was incorrect in this file.Joel Sherrill1-1/+1
1998-01-16Ralf Corsepius reported a number of missing CVS Id's:Joel Sherrill1-0/+3
> RTEMS is under CVS control and has been since rtems 3.1.16 which was > around May 1995. So I just to add the $Id$. If you notice other files > with missing $Id$'s let me know. I try to keep w\up with it. Now that you have asked -- I'll attach a list of files lacking an RCS-Id to this mail. This list has been generated by a little sh-script I'll also enclose.
1997-12-22Removed reference to CC_FOR_TARGET since I don't want anyone overridingJoel Sherrill1-4/+8
it anyway. :) Added hints about --prefix and --program-prefix options.
1997-12-16Corrected minor things including changing RTEMSBSP to RTEMS_BSP.Joel Sherrill1-8/+8
1997-10-08Added comment about using --enable-gcc28 and --enable-libcdirJoel Sherrill1-1/+3
options together.
1997-10-08Updated information on building your own application.Joel Sherrill1-6/+6
1997-08-01Added --enable-gmake-print-directory option and ods68302 bsp.Joel Sherrill1-1/+2
1997-07-31Merged very large and much appreciated patch from Chris JohnsJoel Sherrill1-0/+5
<>. This patch includes the ods68302 bsp, the RTEMS++ class library, and the rtems++ test.
1997-05-27added ka9q stackJoel Sherrill1-0/+4
1997-05-23KA9Q stack removed prior to testing for 4.0.0 public release.Joel Sherrill1-4/+0
1997-04-18Updated to reflect --enable-gcc28 and --enable-libcdir options.Joel Sherrill1-13/+22
1997-04-16Added --disable-tcpip option.Joel Sherrill1-5/+45
Add discussion of the pecularities of the i386-go32-rtems configuration.
1997-04-01This set of changes is the build of what was required to convert toJoel Sherrill1-0/+179
GNU autoconf. This is the first large step in allowing an RTEMS user to perform a one-tree build (per crossgcc FAQ) including RTEMS in the build process. With this change RTEMS is configured in built in the same style as the GNU tools, yet retains the basic structure of its traditional Makefiles (ala Tony Bennett). Jiri Gaisler ( deserves (and received) a big thank you for doing this. There are still issues to be resolved but as of this commit, all target which can be built on a linux host have been using a modified version of the source Jiri submitted. This source was merged and most targets built in the tree before this commit. There are some issues which remain to be resolved but they are primarily related to host OS dependencies, script issues, the use of gawk for hack_specs, and the dependence on gcc snapshots. These will be resolved.