path: root/c/src/lib/libbsp/m68k/efi332/spurious
diff options
authorJoel Sherrill <>1999-03-19 22:01:26 +0000
committerJoel Sherrill <>1999-03-19 22:01:26 +0000
commite619c2895b9109b5008eac9244bfb6719d39ea9b (patch)
treeeb4764c751d852661ac109cd6f39b94262f12261 /c/src/lib/libbsp/m68k/efi332/spurious
parent9ec964784bf2091673a83241ab113f422b1f84d8 (diff)
Towards automake IX patch from Ralf Corsepius <>:
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.
Diffstat (limited to 'c/src/lib/libbsp/m68k/efi332/spurious')
0 files changed, 0 insertions, 0 deletions