summaryrefslogtreecommitdiffstats
path: root/make/custom/efi68k.cfg (follow)
Commit message (Collapse)AuthorAgeFilesLines
* After investigating a problem reported by Franck Julien <FranckJ@cxr.fr>,Joel Sherrill2000-04-161-1/+3
| | | | | | | | I discovered that when specifying -m68000 and -msoft-float to gcc 2.95.2, it decides that the proper multilib variant is the default one which is compiled for the m68020 and hardware floating point. This appears to be because there is no 68000/soft-float library variant. This problem applies to all m68000 class CPUs options including -m68302.
* Patch rtems-rc-4.5.0-6-cvs.diff from Ralf Corsepius <corsepiu@faw.uni-ulm.de>.Joel Sherrill2000-04-031-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | The patch contains: * build variants support * Reworked make-exe custom/*.cfg for all targets (Should be self-explanatory, may still be incomplete) * Several fixes to custom/*.cfgs related to setting debug flags * Fixes to some bsp_specs for BSPs which apparently have never been build with debugging before ;) * pc386.cfg fix attempts (cf. my mail from earlier today) * Updated ampolish (No need to run it, the patch contains the result from having applied it) Known bugs/deficiencies related to this work: * "make [clean|distclean]" support is still incomplete (e.g. "make clean" does not delete all Depends-o-*) * Completely untested for linux/posix and hppa. * Build failures of i960 BSPs (make VARIANT=DEBUG) - I guess, they are not related to this patch. * Successfully tested for all sh, sparc, i386, ppc, m68k BSPs (make VARIANT=DEBUG) * make VARIANT=PROFILE not supported by all BSPs (I don't care :) * make VARIANT=DEBUG failures below tests/ for some BSPs (e.g. gensh1), because of the tests's binaries being too large to fit into the target memory layout.
* Patches rtems-rc-4.5.0-1.diff from Ralf Corsepius <corsepiu@faw.uni-ulm.de>Joel Sherrill2000-02-251-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | that fixes numerous miscellaneous issues most related to the debug and profile build stanzas: Fix for the "make debug" (1) issue and an analogous issue with "make profile" (untested). * Fixes to mcp750.cfg (make debug, directories) (2) * Updates/minor fixes for shgen (3) * Updates some custom/*.cfgs to use $(LINK.c) instead of $(CC) * Leftovers from rtems-rc-4.5.0-[0|1].diff which somehow did not make it into cvs. * Cleanups to the perlscripts below tools/update/ * Some unsorted minor fixes. Footnotes/Remarks: (1) Tested for all m68k, sh, sparc, unix and selected i386, ppc BSPs. Known problems: I can't build the debug variant for the m68k/mvme162 and m68k/mvme162lx (segmentation fault - signal 11 :) (2) Tested by building the BSP, but I doubt the debug-variant is functional. The flags used for the debug variant should be checked by knowledgeable persons and probably at runtime #:o) (3) I have updated shgen to use getopt_long (it should fall back to getopt if not available), enhanced the options, cleaned up some minor tweaks and added help2man support (rough automatic man-page generation). Technical notes: * make debug and make profile now work similar in target Makefile.ams as they did in old autoconf-Makefile.ins using leaf.cfg. Unlike the rules in leaf.cfg these Makefile.am also recurse once on themselves in directory Makefiles before or after recursing into subdirectories, not only in leaf-directories. To implement this behavior, I renamed the former automake/local.am into automake/host.am and extended local.am to provide this recursion. I.e. host.am implements the non-self-recursive variant, while local.am now implements the self-recursive behavior. => all Makefile.ams exploiting build-variants are supposed to include local.am => all Makefile.ams not exploiting build-variants should include host.am => Rules of thumb: - Only include one of both, either local.am or host.am into a Makefile.am. -Target-Makefile.ams should include local.am -Host-Makefile.ams should include host.am (Probably, you now understand the naming) - There are exceptions from these rules :) * Now, make debug|profile|all are independent of each other. However, each of them however triggers preinstall. * "make install" still decends into the subdirectories but does not trigger "all|profile|debug|preinstall" in target Makefile.am anymore. Besides triggering "install"-rules in some selected Makefile.ams, it only packs $(PROJECT_ROOT) into a tarballs and unpacks it to $(prefix). => "make install" alone is not enough to install RTEMS, now use make RTEMS_BSP=<bsps> [all] [debug] [profile] make RTEMS_BSP=<bsp> install I consider this to be a step back wrt. exploiting automake mechanisms, and expect this to be reverted if we abandon building target variants in favour of the standard convention of optionally overriding flags from the command line (i.e. instead of "make debug", GNU standards favor "make CFLAGS=<options> --prefix=<location>")
* Removed need for START_BASE.Joel Sherrill1999-11-221-3/+0
|
* Patch rtems-rc-19990709-6-diff from Ralf Corsepius <corsepiu@faw.uni-ulm.de>Joel Sherrill1999-08-061-4/+0
| | | | | applied. This modified many Makefiles and custom files and makes many more settings (network, multiprocessing, etc) gnerated by autoconf.
* Added $(CPPFLAGS) to all gcc 2.8 style make-exe rules.Joel Sherrill1999-03-081-1/+1
|
* Part of automake VI Patch from Ralf Corsepius <corsepiu@faw.uni-ulm.de>.Joel Sherrill1999-02-181-2/+2
| | | | | | | > Adds variables to the custom/*cfg files to specify the location of > tools. The purpose is to remove hard-coded paths from the Makefiles. > > In later steps this eases moving the tools to other locations.
* Patches from Eric NorumJoel Sherrill1998-08-201-4/+0
|
* FreeBSD stack compiles for the first time (except libc/strsep.c)Joel Sherrill1998-08-201-0/+4
|
* Monstrous patch from Ralf Corsepius <corsepiu@faw.uni-ulm.de>. I haveJoel Sherrill1998-06-271-1/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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/target.cfg.in, 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/Makefile.in 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.) * rtems-glom.in 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/*.cfg.in 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 configure.in. * 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 configure.in, as I suppose there might exist a variety of valid vendors (2nd field of the name-tripple) * Disabled override MAKEFLAGS in toplevel Makefile.in - 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.
* Stack checker now enabled via initial set of user extensions. ThisJoel Sherrill1998-04-151-4/+0
| | | | | eliminates the need to build the entire application with the STACK_CHECKER_ON macro defined.
* Purged references to STACK_CHECKER_REPORT_USAGEJoel Sherrill1998-04-061-5/+0
|
* Removed PROJECT_HOME and CONFIG_DIR variables.Joel Sherrill1998-01-201-0/+83