| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
| |
* .cvsignore: Add autom4te.cache for autoconf > 2.52.
* configure.in: Remove.
* configure.ac: New file, generated from configure.in by autoupdate.
|
| |
|
|
|
| |
* acinclude.m4: New file.
* configure.in: Use RTEMS_BSP_SUBDIR.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
that contains:
* Removes remaining (now illegal) references to $(SRC) from a couple of
Makefile.ams
* Removes duplicate AC_CONFIG_SUBDIRS macro from c/configure.in
* Moves ENABLE_LIBCDIR into RTEMS_PROG_C[C|XX]_FOR_TARGET (hides LIBCDIR
from most configure scripts, i.e. LIBCDIR becomes less visible)
* Adds RTEMS_PROG_C[C|XX]_FOR_TARGET and RTEMS_CANONICALIZE_TOOLS to
libbsp/*/configure.ins (A minor bug in previous implementations, which
only has an impact when switching to GNU/Cygnus canonicalization)
* Cleans up several bogus comments.
* Removes MKLIB
* Switches the version number to 4.5.0 (for testing version number
handling)
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
that contains:
* cleanups to configuration files
* A reworked gccnewlib.spec.in: I have reformated it for enhanced
readability and added more rtems-base packages. It now should be free of
any installation conflicts (If there still remain some, they should be
regarded as bugs).
* A fix to the bin2boot RTEMS_BSP issue (make RTEMS_BSP="pc386 pc486"
now works).
* removes libbsp/bare/wrapup
* Further cleanups
|
|
|
that converts the i960 directory to automake.
The same kind of libbsp configuration as for the mips64orion, now for
the i960.
In addition to libbsp configuration this patch also contains two fixes
for cvme961.cfg and rxgen960.cfg, which contained non-functional
make-exes. (Now both bsps probably have the same issues with linking c++
applications as the gensh2 has, but this is a different open issue not
tried to be solved now).
The rxgen961 also seems to have problems with its start file, because
linking apps fails due to not finding start.o. (Note that
libbsp/i960/rxgen960 lacks a start subdirectory!). I leave solving this
issue to you :)
|
