path: root/tools/cpu (unfollow)
Commit message (Collapse)AuthorFilesLines
1998-06-27Monstrous patch from Ralf Corsepius <>. I haveJoel Sherrill1-1/+1
made no attempt to divide the comments up and place them with just the appropriate files. Here is an excerpt from Ralf's email: Changes including comments on changes I made after cycling through all the targets: * Added ranlib support. Now all targets use "ranlib" instead of "ar -s" to build an index for a library. If ranlib isn't detected during configuration, check if ar -s is working and try "ar -s" instead of * Removed $(XXX_FOR_TARGET) from make/, use $(XXX) instead now. * gcc-target-default.cfg: LINK_XXXX-defines reworked to solve the -l problem under posix (cf gcc-target-default.cfg) * rtems-glom replaced by Makefile-rules inside of the wrapup/ that has been using rtems-glom until now. * Removed CCC and friends in gcc-target-default.cfg, as they have been breaking CXX support. * Removed CONFIG.$(TARGET_ARCH).CC lines from several custom/*.cfg files, because this is now set in custom/default.cfg. * Added aclocal/ar-s.m4, check whether "ar -s" is working * Added aclocal/cygwin.m4 and aclocal/exeext.m4. * Reworked aclocal/canonicalize-tools.m4: Added ar -s check; fixes for problems when XXX_FOR_TARGET is given via environment variables (didn't work for gcc until now), adding cygwin check, improved autoconf-cache handling. * Removed -l from make rule dependencies. LINK_LIBS is now allowed to contain -L and -l. LINK_OBJS and LINK_FILES must not contain -L or -l. gcc28 make-exe rules now link using $(LINK_OBJS) $(LINK_LIBS) => Almost all custom/*.cfg are modified. This is very likely to break something because of typos or having missed to edit a file. Open problems, known bugs, things I didn't do: * custom/p4000.cfg seems to be out of date and requires to be reviewed. (JRS NOTE: It is subordinate p4650 and p4600 -- both of which build ok after minor changes.) * custom/psim.cfg needs to be reviewed, I added some changes to it, I am insecure about. (JRS NOTE: psim had a minor problem endif/endef swapped but runs fine.) * can now be removed. * gcc*.cfg files "make depend" rules don't honor language specific flags (e.g CXXFLAGS is ignored for *.cc) - Nothing to worry about now, but may cause problems for hosts/targets not using gcc or rtems-add-ons that use external packages. * AFAIS, the no_bsp BSP can't be build anymore, i.e. configure refused to configure for it whatever I tried. * The toplevel and toplevel+1 README files are quite out-dated * cygwin.m4 isn't of much use for rtems. In most cases (cf. aclocal/*.m4) it is worked around by directly using $host_os. I think I'll remove it soon after the next snapshot * Before release the cygwin patch needs to be tested under cygwin. I may have broken/missed something (esp. the sed-pattern to convert \\ into / may be broken). * You should try to build/run the posix-BSP under solaris - I don't expect problems, but I am not 100% sure, esp. with regard to ranlib/ar -s. * You should consider to convert all make/compilers/*.cfg files into make/compilers/* files and let autoconf generate the *.cfg. This may help getting rid of some if/then/else statements and help hard-coding some defines into those files in future and shouldn't disturb now. * Not having installed libc.a/libm.a on a host may still break building rtems, esp. when using -disable-gcc28 as the gcc27-configuration scheme directly accesses libc.a and libm.a. The problem should not appear when using gcc28 because it references libc/libm only through -lc and -lm which may be static or dynamic (I didn't test this). * shgen is not yet included (I didn't yet have enough time to integrate it). * I know about a few more configure-probs (esp. cross-checking --enable-* flags). + warn/refuse to configure when --enable-libcdir and --enable-gcc28 are given. + force --enable-libcdir when --disable-gcc28 is given * Replaced KSHELL with @KSH@ in some shell scripts generated by * Added a dependency to aclocal/*.m4 in the toplevel Makefile => configure and aclocal.m4 will now be rebuild when any aclocal/*.m4 file is changed * Some changes to aclocal/gcc-pipe.m4 and aclocal/gcc-specs.m4 * Replaced i[[3456]]86-unknown-freebsd2.[[12]] with i[[3456]]86-*freebsd2.* in, as I suppose there might exist a variety of valid vendors (2nd field of the name-tripple) * Disabled override MAKEFLAGS in toplevel - Potential side-effects are not really clear to me. * In mvme162.cfg, $(LINK_LIBS) is missing in the CC line in gcc28's make-exe rule (yet another one I missed to edit). Just append $(LINK_LIBS) to the "CC" line, like I hopefully did to ALL other custom/*.cfg files. * the problem with mvme162lx.cfg is a follow-up problem of the mvme162.cfg-bug. * mvme162/console and idp/console had variables named Buffer which conflicted with similarly named variables in some tests.
1998-06-18Added freebsd support from Dario Alcocer <>.Joel Sherrill1-0/+7
1998-03-23Renamed hppa1_1 to hppa1.1Joel Sherrill1-4/+1
1998-03-23renamed ppc to powerpcJoel Sherrill1-1/+0
1998-02-27Removed use of dc. David Fiddes reported that this is part of theJoel Sherrill1-1/+17
GNU tool bc which is not always installed under Linux and seldom present under non-UNIX environments like Win32.
1998-02-17updated copyright to 1998Joel Sherrill3-5/+5
1998-02-17Renamed init.o to exinit.o to avoid naming conflicts with tests.Joel Sherrill1-2/+2
1998-02-07Fixed to correctly operate on target variants like debug and profile.Joel Sherrill1-9/+23
1998-01-30Big patch form Ralf Corsepius described in this email:Joel Sherrill3-12/+6
Here is the result of my nightly work to get RTEMS_ROOT=$srcdir working with different shells and relative/absolute paths. What I did is relatively simple in principle: Instead of setting RTEMS_ROOT in and then let configure substitute @RTEMS_ROOT@ inside the Makefiles, I now let each Makefile set RTEMS_ROOT from each Makefile's @top_srcdir@ value. The difference is subtile, but with enormous side effects: - If RTEMS_ROOT is set in configure, then the same single value will be propagated to all Makefiles. This breaks using relative paths, as the relative path to the root of the source tree is used inside of all subdirectory Makefiles. - Now each sets RTEMS_ROOT = @top_srcdir@. top_srcdir is computed individually by configure for each single, hereby receiving the correct value, no matter if relative or absolute paths are used. To get this working, I needed to remove setting RTEMS_ROOT from, because this overrides the value of RTEMS_ROOT from each individual Makefile. Furthermore, I removed RTEMS_CUSTOM from the Makefiles and replaced all "include $(RTEMS_CUSTOM)" directives with"include $(RTEMS_ROOT)/make/custom/$(RTEMS_BSP)". Perhaps you don't like this, but I think, to have one variable less is clearer and easier to understand than having several variables refering to the next one. I enclose a small patch to this mail, which - fixes the config.h problem (to finally clearify misunderstands) - removes assignment/subsitution of RTEMS_ROOT from - contains a workaround for the application Makefile's RTEMS_ROOT problem (reported by Eric) - removes some unused lines from the toplevel - removes assignment of RTEMS_ROOT from make/
1998-01-23Cleaned up a bit.Joel Sherrill1-9/+31
1998-01-20Removed CONFIG_DIR and PROJECT_HOME directories.Joel Sherrill3-3/+3
1997-12-22Now generating this file with autoconf to avoid having to embed soJoel Sherrill1-0/+221
much target specific information in the script.
1997-12-10Modified a lot of files to take a first cut at supporting building fromJoel Sherrill3-3/+12
any directory in the build tree. The only variable which must be set before the command "gmake" is invoked is RTEMS_BSP (e.g. RTEMS_BSP=erc32).
1997-11-30Corrected comment.Joel Sherrill1-4/+0
1997-10-08Fixed typo in the pointer to the license terms.Joel Sherrill2-8/+8
1997-10-08Removed include directory at "build" point and the link of this directoryJoel Sherrill1-1/+1
to lib/include. Went to using a PROJECT_INCLUDE variable.
1997-04-22headers updated to reflect new style copyright notice as partJoel Sherrill2-18/+18
of switching to the modified GNU GPL.
1997-04-07added ifdef around variables to eliminate warnings when crossJoel Sherrill1-0/+2
1997-04-01This set of changes is the build of what was required to convert toJoel Sherrill3-0/+107
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.
1996-05-23*** empty log message ***Joel Sherrill1-2/+2
1996-04-22updates from Tony BennettJoel Sherrill1-6/+35
1995-12-05minor changes so it would compile in a cross environmentJoel Sherrill1-0/+2
1995-09-29all targets compile .. tony's patches in placeJoel Sherrill1-2/+2
1995-09-27Modified UNIX simulator port so all references to native unixJoel Sherrill1-0/+116
stuff is in the executive source proper in the file cpu.c. This should help avoid conflicts between RTEMS POSIX files and UNIX files.
1995-09-12Initial attempt at building HP PA-RISC using Solaris hosted tools.Joel Sherrill1-5/+129
Changed back to Newlib for Solaris UNIX simulator.
1995-08-22Fixed missing RCS IdsJoel Sherrill1-1/+1
1995-05-24Fully tested on all in-house targetsJoel Sherrill1-4/+4