path: root/missing (unfollow)
Commit message (Collapse)AuthorFilesLines
2021-09-21build: Remove old build systemSebastian Huber1-215/+0
Close #3250. Close #4081.
2013-05-27Update from automake-1.13.2.Ralf Corsépius1-260/+145
2012-10-09Import from automake-1.12.4.Ralf Corsépius1-0/+330
2012-08-06Remove generated files.Gedare Bloom1-330/+0
2012-07-19Update from automake-1.12.2.Ralf Corsépius1-50/+49
2012-02-222012-02-22 Ralf Corsépius <>Ralf Corsépius1-0/+331
* .gitignore: Remove config.guess, config.sub, missing, install-sh. * config.guess, config.sub, missing, install-sh: New.
2001-09-212001-09-21 Ralf Corsepius <>Joel Sherrill1-283/+0
* bootstrap: remove/add automake added files. * .cvsignore: reflect changes to bootstrap.
2001-09-132001-09-13 Joel Sherrill <>Joel Sherrill1-8/+101
* missing: Updated to latest version.
1999-03-19Towards automake IX patch from Ralf Corsepius <>:Joel Sherrill1-0/+190
This is the next step towards automake: * Two scripts for the toplevel directory: a) "autogen" (Idea borrowed from libtool and gnome) A helper script to recursively regenerate autoconf/automake/aclocal generated files (Still not perfect but sufficient). b) "missing" (from automake-cvs archive). This file normally is automatically generated by automake, but we have to manually add it until we add automake support to the toplevel configure script. "chmod 755 missing autogen" after applying the patch. * Changing the toplevel installation directory [ I can hear you falling off the chair ;-] Until now rtems installed itself to $(prefix)/rtems. This is in contradiction to automake and GNU/FSF/Cygnus conventions. With this patch applied, rtems installs into $(prefix). To achieve the old behaviour simply configure with --prefix=<install-dir>/rtems instead of --prefix=<install-dir> This is a widely visible change and I can understand if you don't like it at the present point. It enables us to use automake's default installation paths instead of having to set up installation paths manually. At the moment this doesn't help much, but in the not so far future this would enable us to mix cpu-only dependent libraries into the host's cross-compiler library and header files into newlib's include directories, tools into the toolchain directories etc. I would recommend to change the main installation directory, however it's up to you to draw the final design decision.