Go to the first, previous, next, last section, table of contents.

Compilation

After you've run configure, compilation is straightforward. To compile all the programs in the Developer's Kit, run:

make all info > make.log

The examples suggest capturing the make output in a `make.log' file, because the output is lengthy.

make creates a set of binaries which run on your hosttype and which compile code for the specified target (or for the hosttype in a native configuration). Programs which require compiled-in pathnames are built with the values you specified on the command line to configure with the options `--prefix' and `--exec-prefix'. In cross-development configurations, programs are named with target as a prefix; for example, the cross-compiler is named target-gcc.

The overall `Makefile' propagates the value of the CC variable explicitly, so that you can easily control the compiler used in this step. CFLAGS is treated the same way. For instance, to build the compiler a second time, using gcc to compile itself (after building and installing it in the alternate directory `/usr/local'; see section Rebuilding using gcc), you might follow this example:

$ CC=/usr/local/bin/gcc configure ...
$ make CC=/usr/local/bin/gcc CFLAGS=-O2 all info > make.log

Make sure you specify the same compiler for CC for both the configure and make steps.

The conventional targets all, install, and clean are supported at all levels of `Makefile'. (Other targets are supported as well, as appropriate in each directory.) Each `Makefile' in the source directories includes ample comments to help you read it. If you are not familiar with make, refer to section `Overview of make' in GNU Make: A Program for Directing Recompilation.


Go to the first, previous, next, last section, table of contents.