Short overview for those who don't read manuals: Calling configure manually is outdated because this is a task of the makefile system. There is no 'configure', simply call 'make' on the top level directory. ***** If this does not work for you, read the rest if this file ***** ***** If you have any problem, also first read the topic specific ***** ***** README.* files (e.g. README.linux for Linux problems). ***** All results in general will be placed into a directory named OBJ/<arch-name>/ in the current projects leaf directory. You **need** either my "smake" program, the SunPRO make from /usr/bin/make (SunOS 4.x) or /usr/ccs/bin/make (SunOS 5.x) or GNU make to compile this program. Read READMEs/README.gmake for more information on gmake and a list of the most annoying bugs in gmake. All other make programs are either not smart enough or have bugs. My "smake" source is at: ftp://ftp.berlios.de/pub/smake/alpha/ It is easy to compile and doesn't need a working make program on your machine. If you don't have a working "make" program on the machine where you like to compile "smake" read the file "BOOTSTRAP". If you have the choice between all three make programs, the preference would be 1) smake (preferred) 2) SunPRO make 3) GNU make (this is the last resort) Important notice: "smake" that comes with SGI/IRIX will not work!!! This is not the Schily "smake" but a dumb make program from SGI. ***** If you are on a platform that is not yet known by the ***** ***** Schily makefilesystem you cannot use GNU make. ***** ***** In this case, the automake features of smake are required. ***** Please read the README's for your operating system too. WARNING Do not use 'mc' to extract the tar file! All mc versions before 4.0.14 cannot extract symbolic links correctly. The versions of WinZip that support tar archives cannot be used too. The reason is that they don't support symbolic links. Star and Gnutar do support symbolic links even on win32 systems. To support symbolic links on win32, you need to link with the Cygwin32 POSIX library. To unpack an archive use: gzip -d < some-arch.tar.gz | tar -xpf - Replace 'star' by the actual archive name. If your Platform does not support hard links or symbolic links, you first need to compile "star" and then call: star -xpz -copy-links < some-arch.tar.gz If your platform does not support hard links but supports symbolic links, you only need to call the command above once. If your platform does not support symbolic links, you need to call the command twice because a symbolic link may occur in the archive before the file it points to. Here comes the long form: PREFACE: Calling configure manually is outdated because this is a task of the makefile system. You don't have to call configure with this make file system. Calling 'make' or 'make all' on the top level directory will create all needed targets. Calling 'make install' will install all needed files. This program uses a new makefilesystem. This makefilesystem uses techniques and ideas from the 1980s and 1990s, is designed in a modular way and allows sources to be combined in a modular way. For mor information on the modular features read README.SSPM. The makefilesystem is optimized for a program called 'smake' Copyright 1985 by Jörg Schilling, but SunPro make (the make program that comes with SunOS >= 4.0 and Solaris) as well as newer versions of GNU make will work also. BSDmake could be made working, if it supports pattern matching rules correctly. The makefile system allows simultaneous compilation on a wide variety of target systems if the source tree is accessible via NFS. Finding Compilation Results: To allow this, all binaries and results of a 'compilation' in any form are placed in sub-directories. This includes automatically generated include files. Results in general will be placed into a directory named OBJ/<arch-name>/ in the current projects leaf directory, libraries will be placed into a directory called libs/<arch-name>/ that is located in the source tree root directory. <arch-name> will be something like 'sparc-sunos5-cc' This is the main reason why simultaneous compilation is possible on all supported platforms if the source is mounted via NFS. How to compile: To compile a system or sub-system, simply enter 'smake', 'make' or 'Gmake'. Compilation may be initialized at any point of the source tree of a system. If compilation is started in a sub tree, all objects in that sub tree will be made. How to install results: To install the product of a compilation in your system, call: smake install at top level. The binaries will usually be installed in /opt/schily/bin. The directory /opt/<vendor-name>/ has been agreed on by all major UNIX vendors in 1989. Unfortunately, still not all vendors follow this agreement. If you want to change the default installation directory, edit the appropriate (system dependent) files in the DEFAULTS directory (e.g. DEFAULTS/Defaults.sunos5). ***** If "smake install" doesn't do anything, you are on a broken ***** ***** File System. Remove the file INSTALL in this case (the FS ***** ***** does not handle upper/lower case characters correctly). ***** ***** This is true for all DOS based filesystems and for Apple's ***** ***** HFS+ filesystem. ***** Using a different installation directory: If your system does not yet use the standard installation path /opt or if you don't like this installation directory, you can easily change the installation directory. You may edit the DEFAULTS file for your system and modify the macro INS_BASE. You may use a different installation directory without editing the DEFAULTS files. If you like to install everything in /usr/local, call: If your make program supports to propagate make macros to sub make programs which is the case for recent smake releases as well as for a recent gnumake: smake INS_BASE=/usr/local install or gmake INS_BASE=/usr/local install If you make program doesn't propagate make macros (e.g. SunPRO make) call: env INS_BASE=/usr/local make -e install Note that INS_BASE=/usr/local needs to be specified for every operation that compiles or links programs as the path is stored inside the binaries. The location for the root specific configuratin files is controlled via the INS_RBASE= make macro. The default vaulue for this macro is "/". If you like to install global default configuration files into /usr/local/etc instead of /etc, you need to spefify INS_RBASE=/usr/local Note that some binaries have $(INS_BASE) and $(INS_RBASE) compiled into. If you like to like to modify the compiled-in path values, call: smake clean smake INS_BASE=/usr/local INS_RBASE=/usr/local Compiling in a different ELF RUNPATH: In order to allow binaries to work correctly even if the shared libraries are not in the default search path of the runtime linker, a RUINPATH needs to be set. The ELF RUNPATH is by default derived from $(INS_BASE). If you like to set INS_BASE=/usr and create binaries that do not include a RUNPATH at all, call: smake relink RUNPATH= Using a different man path prefix: Man Pages are by default installed under: $(INS_BASE)/$(MANBASE)/man and MANBASE=share If you like a different prefix for man pages, call: smake DEFMANBASE=soething install to install man pages into $(INS_BASE)/something/man/* If you like to install man pages under $(INS_BASE)/man/*, call smake DEFMANBASE=. install Installing stripped binaries: If you like to install stripped binaries via "smake install", call: smake STRIPFLAGS=-s install This calls "strip" on every final install path for all executable binaries. Installing to a prototype directory to implement package creation staging: If you like to create a prototype directory tree that is used as an intermediate store for package creation, use the DESTDIR macro: smake INS_BASE=/usr/local DESTDIR=/tmp install This will compile in "/usr/local" as prefix into all related binaries and then create a usr/local tree below /tmp (i.e. /tmp/usr/local). Note that you need to call "smake clean" before in case that the code was previously compiled with different defaults. Setting different default directory permissions for install directories: All directories that are created by the Schily makefile system in the target directory path when smake install is called system use a special default 022 that is in DEFINSUMASK= This causes all directories in the target install path to be created with 0755 permissions. All other directories that are created by the Schily makefile system use a single global default 002 that is in DEFUMASK= If you like to create install directories with e.g. 0775 permissions, call: smake DEFINSUMASK=002 install Using a different C-compiler: If the configured default compiler is not present on the current machine, the makefilesystem will try an automatic fallback to GCC. For this reason in most cases you will not need to manually select a compiler. The default C-compiler can be modified in the files in the DEFAULT directory. If you want to have a different compiler for one compilation, call: make CCOM=gcc or make CCOM=cc This works even when your make program doesn't propagate make macros. Creating 64 bit executables on Solaris: Simply call: make CCOM=gcc64 or make CCOM=cc64 It is not clear if GCC already supports other platforms in 64 bit mode. As all GCC versions before 3.1 did emit hundreds of compilation warnings related to 64 bit bugs when compiling itself, there is little hope that other platforms are already supported in 64 bit mode. Creating executables using the Sun Studio compiler on Linux: Simply call: make CCOM=suncc If the compilation does not work, try: mkdir /opt/sunstudio12/prod/include/cc/linux cp /usr/include/linux/types.h /opt/sunstudio12/prod/include/cc/linux Then edit /opt/sunstudio12/prod/include/cc/linux/types.h and remove all lines like: "#if defined(__GNUC__) && !defined(__STRICT_ANSI__)" as well as the related #endif. Getting help from make: For a list of targets call: make .help Getting more information on the make file system: The man page makefiles.4 located in man/man4/makefiles.4 contains the documentation on general use and for leaf makefiles. The man page makerules.4 located in man/man4/makerules.4 contains the documentation for system programmers who want to modify the make rules of the makefile system. For further information read ftp://ftp.berlios.de/pub/makefiles/PortableSoftware.ps.gz Hints for compilation: The makefile system is optimized for 'smake'. Smake will give the fastest processing and best debugging output. SunPro make will work as is. GNU make need some special preparation. Read READMEs/README.gmake for more information on gmake. To use GNU make create a file called 'Gmake' in your search path that contains: #!/bin/sh MAKEPROG=gmake export MAKEPROG exec gmake "$@" and call 'Gmake' instead of gmake. On Linux there is no gmake, 'make' on Linux is really a gmake. 'Gmake' and 'Gmake.linux' are part of this distribution. Some versions of gmake are very buggy. There are e.g. versions of gmake on some architectures that will not correctly recognize the default target. In this case call 'make all' or ../Gmake all'. Note that pseudo error messages from gmake similar to: gmake[1]: Entering directory `cdrtools-1.10/conf' ../RULES/rules.cnf:58: ../incs/sparc-sunos5-cc/Inull: No such file or directory ../RULES/rules.cnf:59: ../incs/sparc-sunos5-cc/rules.cnf: No such file or directory Are a result of a bug un GNU make. The make file system itself is correct (as you could prove by using smake). If your gmake version still has this bug, send a bug report to: "Paul D. Smith" <psmith@gnu.org> He is the current GNU make maintainer. If you like to use 'smake', please always compile it from source. The packages are located on: ftp://ftp.berlios.de/pub/smake/alpha/ Smake has a -D flag to see the actual makefile source used and a -d flag that gives easy to read debugging info. Use smake -xM to get a makefile dependency list. Try smake -help Compiling the project using engineering defaults: The defaults found in the directory DEFAULTS are configured to give minimum warnings. This is made because many people will be irritated by warning messages and because the GNU c-compiler will give warnings for perfectly correct and portable c-code. If you want to port code to new platforms or do engineering on the code, you should use the alternate set of defaults found in the directory DEFAULTS_ENG. You may do this permanently by renaming the directories or for one compilation by calling: make DEFAULTSDIR=DEFAULTS_ENG Compiling the project to allow debugging with dbx/gdb: If you like to compile with debugging information for dbx or gdb, call: make clean make COPTX=-g LDOPTX=-g Creting Blastwave packages: Call: .clean smake -f Mcsw You need the program "fakeroot" and will find the results in packages/<arch-dir> Note that a single program source tree will allow you to create packages like CSWstar but not the packages CSWschilybase and CSWschilyutils on which CSWstar depends. If you want to see an example, please have a look at the "star" source. It may be found on: ftp://ftp.berlios.de/pub/star Have a look at the manual page, it is included in the distribution. Install the manual page with make install first and include /opt/schily/man in your MANPATH Note that some systems (e.g. Solaris 2.x) require you either to call /usr/lib/makewhatis /opt/schily/man or to call man -F <man-page-name> Author: Joerg Schilling Seestr. 110 D-13353 Berlin Germany Email: joerg@schily.isdn.cs.tu-berlin.de, js@cs.tu-berlin.de joerg.schilling@fokus.fraunhufer.de Please mail bugs and suggestions to me.