summaryrefslogtreecommitdiffstats
path: root/Makefile.in (follow)
Commit message (Collapse)AuthorAgeFilesLines
* Patch from Eric VALETTE <valette@crf.canon.fr>:Joel Sherrill1998-07-231-1/+1
| | | | | | | | | | | | | Here is a enhanced version of my previous patch. This patch enables to potentially share the new interrupt management code for all Intel targets (pc386, go32 and force386) bsp. Note : this patch is complete only for pc386. It still needs to be completed for go32 and force386. I carrefully checked that anything needed is in for force386 (only some function name changes for IDT manipulation and GDT segment manipulation). But anyway I will not be able to test any of theses targets...
* Monstrous patch from Ralf Corsepius <corsepiu@faw.uni-ulm.de>. I haveJoel Sherrill1998-06-271-3/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
* New autoconf feature from Ralf Corsepius:Joel Sherrill1998-02-041-0/+22
| | | | | | | | | | | | | | | | | | | | It adds make rules for reconfiguring build-trees ("make Makefile") and adds dependency rules for configure and friends (i.e. calls autoconf). Most of this code has been "borrowed" from automake and was adapted to rtems. Addionally, I added automatic generation of the "aclocal.m4"-file by "aclocal" (from the automake package). Therefore I splitted aclocal.m4 into several separate files (attached to this mail), each containing one of rtems customized autoconf/m4-macros and have put them into a new subdirectory "aclocal". Normal users won't be influenced and won't even need this, unless they try to modify configure.in. The main advantage of this is: these aclocal/m4-macros become reusable and easier to administer. As a disadvantage, rtems becomes dependent of having aclocal/automake installed. To keep building rtems functional if autoconf or aclocal isn't installed, the related Makefile commands are prefixed by "-" -- only an error message should be issued by "make".
* Big patch form Ralf Corsepius described in this email:Joel Sherrill1998-01-301-7/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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 configure.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 Makefile.in sets RTEMS_ROOT = @top_srcdir@. top_srcdir is computed individually by configure for each single Makefile.in, 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 target.cfg.in, 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 configure.in - contains a workaround for the application Makefile's RTEMS_ROOT problem (reported by Eric) - removes some unused lines from the toplevel Makefile.in - removes assignment of RTEMS_ROOT from make/target.cfg.in
* Removed some stanzas per Ralf Corsepius:Joel Sherrill1998-01-271-18/+2
| | | | | | | > 4) The toplevel Makefile.in contains rules named make_subdir and > clean_modules, which probably can be deleted, IMO. > At least make_subdir doesn't give any sense anymore. (I had removed it > im my original patch).
* Solaris port updates from Chris JohnsJoel Sherrill1998-01-231-0/+2
|
* Ralf Corsepius reported a number of missing CVS Id's:Joel Sherrill1998-01-161-0/+2
| | | | | | | | | | > RTEMS is under CVS control and has been since rtems 3.1.16 which was > around May 1995. So I just to add the $Id$. If you notice other files > with missing $Id$'s let me know. I try to keep w\up with it. Now that you have asked -- I'll attach a list of files lacking an RCS-Id to this mail. This list has been generated by a little sh-script I'll also enclose.
* Ralf Corsepius <corsepiu@faw.uni-ulm.de> suggested removing theseJoel Sherrill1998-01-151-2/+0
| | | | | lines so setting RTEMS_BSP in an environment variable works even from the top level directory.
* Switched command line override variable RTEMSBSP to RTEMS_BSPJoel Sherrill1997-12-161-3/+3
| | | | | and internally generated list of BSPs to RTEMS_BSP_LIST to make BSP override from the top level directory consistent.
* Modified a lot of files to take a first cut at supporting building fromJoel Sherrill1997-12-101-52/+8
| | | | | 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).
* Serious cleanup to reduce the number of explicitly listed Makefiles,Joel Sherrill1997-11-301-8/+4
| | | | | eliminated autoconf looking for commands which are unused, and reduce the number of Makefiles generated.
* Changes from Ralf Corsepius (corsepiu@faw.uni-ulm.de) to automaticallyJoel Sherrill1997-11-291-2/+4
| | | | generate the list of Makefiles in the configure script.
* Renamed mlink to make_subdir.Joel Sherrill1997-10-081-4/+3
| | | | Removed a junk line.
* Reworked building of make subdirectory and contents in the objectJoel Sherrill1997-10-081-1/+11
| | | | tree.
* Removed duplicate listing of install in MTARGETS.Joel Sherrill1997-09-211-2/+2
| | | | Add monitor test.
* Added support for TARGET_VARIANTS.Joel Sherrill1997-08-261-2/+3
|
* Merged very large and much appreciated patch from Chris JohnsJoel Sherrill1997-07-311-0/+4
| | | | | <cjohns@plessey.com.au>. This patch includes the ods68302 bsp, the RTEMS++ class library, and the rtems++ test.
* added ka9q stackJoel Sherrill1997-05-271-0/+2
|
* KA9Q stack removed prior to testing for 4.0.0 public release.Joel Sherrill1997-05-231-2/+0
|
* Updated to point to README.configure for build instructions.Joel Sherrill1997-04-251-1/+1
|
* Modifications to add --enable-libcdir and --enable-gcc28. TheseJoel Sherrill1997-04-181-0/+4
| | | | | trip options which allow the RTEMS makefile structure to support both gcc 2.7.2.2 and gcc 2.8 whenever that is released.
* blank lines deletedJoel Sherrill1997-04-091-2/+0
|
* Added ka9q tcpip stack and network driver for the gen68360. This effortJoel Sherrill1997-04-091-0/+2
| | | | | | | | | | | | | was done based on the 3.6.0 release and had to be autoconf'ed locally. It is turned on is the bsp enables it and it is not explicitly disabled via the configure option --disable-tcpip. As many warnings as possible were removed locally after the code was merged. Only the gen68360 and mvme136 bsps were compiled this way. The ka9q port and network driver were submitted by Eric Norum (eric@skatter.USask.Ca). The network demo programs are not included in the tree at this point.
* This set of changes is the build of what was required to convert toJoel Sherrill1997-04-011-0/+99
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 (jgais@wd.estec.esa.nl) 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.