How to download, compile and install GNU Pascal.

ftp://agnes.dida.physik.uni-essen.de/gnu-pascal/libs/

• the C library, `v2/djdev201.zip', and
• `binutils' (assembler, etc.), `v2gnu/bnu270b.zip'.

• the `make' utility, `v2gnu/mak375b.zip'
• the GNU debugger, `v2gnu/gdb416b.zip'
• the DJGPP FAQ, `v2faq/faq211b.zip'
• the GRX graphics library, http://www.gnu.de/software/GRX/
• @localuref{misc.html#PENG,`PENG'}, http://fjf.gnu.de/peng.html, an integrated development environment, similar to BP's one, written in GNU Pascal, or
• @localuref{misc.html#RHIDE,`RHIDE'}, `v2app/rhide.zip', another integrated development environment.

http://www.leo.org/pub/comp/os/os2/leo/gnu/emx+gcc/index.html

• the EMX runtime package, `emxrt.zip',
• the EMX development system, `emxdev*.zip', and
• the GNU development tools, `gnudev*.zip'.

http://www.cygnus.com/cygwin/

http://agnes.dida.physik.uni-essen.de/~janjaap/mingw32/
http://www.xraylith.wisc.edu/~khan/software/gnu-win32/

Installation instructions for a GPC binary distribution

To install a binary distribution, cd to the root directory and unpack the archive while preserving the stored directory structure. Under a Unix compatible system with GNU tar installed, the following (performed as `root') will do the job:

# cd /
# tar xzf archive.tar.gz

If you are using a `tar' utility other than GNU tar, it might be necessary to do the above in an explicit pipe:

# cd /
# gzip -c -d archive.tar.gz | tar xf -

If you want to install a GPC binary distribution in another directory than it was prepared for (for example, if you do not have root access to the computer and want to install GPC somewhere under your home directory), you can do the following:

• Unpack the archive file in a directory of your choice (see above).
• `cd' to the "prefix" directory of the distribution (for instance `usr/local').
• Run the script install-gpc-binary, available from ftp://agnes.dida.physik.uni-essen.de/gnu-pascal/current/binary/.
• Follow the instructions in the script.

To install a ZIP archive under DOS with `PKunzip', `cd' the the appropriate directory (usually `\' for EMX, `\DJGPP' for DJGPP), then call `PKunzip' with the `-d' option:

C:\> cd djgpp
C:\DJGPP> pkunzip -d archive.zip

where `archive.zip' is the name of the distribution file.

For DJGPP you must edit your `djgpp.env' in the `DJGPP' directory to complete the installation: Please copy the entries from `[gcc]' to create a new `[gpc]' section. The result may look as follows:

[gcc]
COMPILER_PATH=%/>;COMPILER_PATH%%DJDIR%/bin
LIBRARY_PATH=%/>;LIBRARY_PATH%%DJDIR%/lib

[gpc]
COMPILER_PATH=%/>;COMPILER_PATH%%DJDIR%/bin
LIBRARY_PATH=%/>;LIBRARY_PATH%%DJDIR%/lib

If you are using the DJGPP version of GPC but do not have a `DJGPP' directory, please download and install DJGPP (see section Where and what to download).

Binary distributions include `libgcc.a' and `specs', files that are normally part of GCC. If you have GCC installed, they will be replaced unless you manually install the archive.

Compiling GPC

The preferred way to distribute GNU software is distribution of the source code. However, it can be a non-trivial exercise to build GNU Pascal on some non-Unix systems, so we also provide ready-to-run binaries for a number of platforms. (See section Installation instructions for a GPC binary distribution for how to install a binary distribution.)

GPC is based on the GNU Compiler Collection, GNU CC or GCC. You will need the GCC sources to build it. It must be the same version as the one GPC is implemented with -- version 2.95.x as of this writing. Although you need GCC to build the GNU Pascal compiler, you don't need GCC to compile Pascal programs once GNU Pascal is installed. (However, using certain libraries will require compiling C wrappers, so it is a good idea to install the C compiler as well.)

Because GNU Pascal shares its back-end with GCC, it should run on any system supported by GCC. A full list of platforms supported by GCC can be found in section `Chapter 4' in "Using and Porting GNU CC".

The GCC source can be obtained from any mirror of the GNU FTP site, ftp://ftp.gnu.org/gnu/gcc/. The "core" distribution is sufficient for GPC.

Here is the generic procedure for installing GNU Pascal on a Unix system. See section Compilation notes for specific platforms for extra information needed to install GPC on DOS-like platforms.

1. Checking the prerequisites Make sure that GNU make is installed. (In the following, we will simply speak of `make' when invoking GNU make; you might need to call `gmake' instead.) For extracting the example programs from the documentation to the `doc/docdemos' directory a non-crippled `sed' is needed. GNU sed is known to work. If you have checked out the GPC source from CVS, you will have to rebuild most derived files, so you will need additional tools: `bison', `flex', `makeinfo', `gperf', and `autoconf'. Make sure that these are installed. If you want to build the GPC WWW pages you will also need: `texi2html' version 1.61 (older versions are missing some needed features; newer versions suffer from a bug), `texi2dvi', TeX, `gzip', `dvips', `dviselect', and `dviconcat'. If you run into trouble during the installation process, please check whether you are using outdated versions of the required utilities and upgrade if necessary. The GNU versions of the packages above are available from the GNU FTP server or any of its mirrors. Package package is usually located in the directory `gnu/package'.
2. Unpacking the source From a directory of your choice (e.g. `/home/fred'), unpack the GCC and GNU Pascal source distributions. This will create separate subdirectories for GCC and GPC. Let us assume `gcc-2.95.1' and `gpc-20000535' in this example.

   % cd /home/fred
   % gzip -c -d gcc-core-2.95.1.tar.gz | tar xf -
   % gzip -c -d gpc-20000535.tar.gz | tar xf -
   

   `cd' to the GPC directory and move the contents (a subdirectory `p') to the subdirectory `gcc' of the GCC directory:

   % cd /home/fred/gpc-20000535
   % mv p /home/fred/gcc-2.95.1/gcc/
   

   It is recommended, though not required, to use a separate directory for building the compiler, rather than compiling in the source directory. In this example, let us create `/home/fred/gpc-build' for this purpose:

   % mkdir /home/fred/gpc-build
   

   If you use a separate directory, you do not need to write into the GCC source directory once you have patched the GCC source (see below), and can build GPC for more than one platform from the same source tree. In case you are re-using a directory where you have already built GCC and/or GPC for a different target machine, do `make distclean' to delete all files that might be invalid. One of the files this deletes is `Makefile'; if `make distclean' complains that `Makefile' does not exist, it probably means that the directory is already suitably clean.
3. Configuring and building GCC GNU Pascal is automatically configured with GCC. Configuration of GCC is treated in depth in section `Chapter 4' in "Using and Porting GNU CC". The normal procedure is as follows: `cd' to the GPC build directory. From there, run the `configure' script in the GCC source directory:

   % cd /home/fred/gpc-build
   % /home/fred/gcc-2.95.1/configure --enable-languages=pascal
   

   This creates all the necessary config files, links and Makefile in the GCC object directory. Note 1: The configuration will prompt you for patching the GCC source for GPC support, so you need write access to that directory. All changes to GCC are surrounded by `#ifdef GPC ... #endif', so they should not interfere when you build a C compiler from this source tree. Note 2: The `--enable-languages=pascal' option means that we only want to build the Pascal compiler and not, for instance, the C++ compiler. Note 3: The standard base directory for installing GCC and GPC is `/usr/local'. If you want to install files to an alternate directory dir, specify `--prefix=dir' when you run `configure'.
4. Putting other GNU tools in place Some environments require other GNU tools (such as the GNU assembler or linker) instead of the standard system tools for GCC to work. (See the GCC installation instructions for details.) If this is the case for your system, install the required tools in the GPC build directory under the names `as', `ld', or whatever is appropriate. This will enable the compiler to find the proper tools for compilation of the program `enquire' (a part of GCC) and to install the GNU tools to a place where they are found by GCC but do not interfere with the standard system tools. Alternatively, you can do subsequent compilation using a value of the PATH environment variable such that the necessary GNU tools come before the standard system tools.
5. Compiling GPC Once you are satisfied with the configuration as determined by `configure', you can build the compiler:

   % make
   

   Notice that this procedure will build the C compiler (and maybe some other compilers) too, because that is used to compile the GPC runtime library. Optionally, you may supply CFLAGS, LDFLAGS or RTSFLAGS. CFLAGS is used for compiler and RTS, RTSFLAGS are for RTS only, i.e.: `make CFLAGS="-O2" RTSFLAGS=-Wall'
6. Completing the installation When everything has been compiled, you can check the installation process with:

   % make -n install
   

   To complete the installation, run the command `make install'. You need write access to the target directories (`/usr/local/bin', `/usr/local/lib', `/usr/local/info', `/usr/local/doc', and `/usr/local/man' in this example), so this is usually done as `root':

   % su -c "make install"
   

   If you want to install only the Pascal compiler (for example if you already have the correct version of GCC installed), `cd' to the `gcc' subdirectory of the build directory (e.g. `/home/fred/gpc-build/gcc') and run `make pascal.install'. This installation process does not overwrite existing copies of `libgcc.a' or `specs', should they exist. Also from the `gcc' subdirectory you can do some more "exotic" builds. For instance, you can build the GPC WWW pages by typing `make pascal.html' or a binary distribution by typing `make pascal.bindist'. See the `Makefile' in that directory for more examples.

Compilation notes for specific platforms

MS-DOS with DJGPP

The only compiler that is capable of compiling the GNU Compiler Collection (GNU CC or GCC) under MS-DOS is GCC itself. In order to compile GPC or GCC for MS-DOS with DJGPP you will therefore need either a working copy of DJGPP installed, or you will have to cross-build from a non-MS-DOS system.

Building GPC under MS-DOS with DJGPP follows the same scheme as building GPC under a Unix-like system: Place the `p' subdirectory in the `gcc' directory and follow the instructions for compiling GCC. This requires `bash' and many other tools installed, and you must be very careful at many places to circumvent the limitations of the DOS platform.

Our preferred way to build GPC for DJGPP is to cross-build it from a Unix-like platform -- which is much easier. For instructions, see section Building and Installing a cross-compiler and section Crossbuilding a compiler..

MS-DOS or OS/2 with EMX

EMX is a free 32-bit DOS extender which adds some properties of Unix to MS-compatible DOS and IBM's OS/2 operating systems.

As of this writing, we are not aware of current versions of GCC for EMX, and EMX support in GPC has not been maintained. Please contact us if you know about recent development in EMX and are interested in continuing EMX support in GPC.

MS Windows 95/98/NT

There are two ports of the GNU development tools to MS Windows 95/98/NT: CygWin and mingw32.

The CygWin environment implements a POSIX layer under MS Windows, giving it large parts of the functionality of Unix. Thus, compiling GCC and GPC under the CygWin environment can be done following the instructions for compiling it under a Unix-like system (see section Compiling GPC).

The Minimalists' GNU Win32 environment, mingw32, uses the native `crtdll.dll' library of MS Winodws. It is much smaller than CygWin, but it is not self-hosting and must be crossbuilt from another system (see section Crossbuilding a compiler.).

Building and Installing a cross-compiler

GNU Pascal can function as a cross-compiler for many machines. Information about GNU tools in a cross-configuration can be found at `ftp://ftp.cygnus.com/pub/embedded/crossgcc/'.

Since GNU Pascal generates assembler code, you need a cross-assembler that GNU Pascal can run, in order to produce object files. If you want to link on other than the target machine, you need a cross-linker as well. It is straightforward to install the GNU binutils to act as cross-tools -- see the installation instructions of the GNU binutils for details.

You also need header files and libraries suitable for the target machine that you can install on the host machine. Please install them under `prefix/platform/include/', for instance `/usr/local/i386-pc-msdosdjgpp/include/' for a cross-compiler from a typical Unix-like environmant to MS-DOS with DJGPP.

Configuration and compilation of the compiler can then be done using the scripts `cfgpc' and `mkgpc' which are included in the source distribution in the subdirectory `p/script'. Please call them with the `-h' option for instructions.

Crossbuilding a compiler.

Using a cross-compiler to build GNU Pascal results in a compiler binary that runs on the cross-target platform. This is called "crossbuilding". A possible reason why anybody would want to do this, is when the platform on which you want to run the GNU Pascal compiler is not self-hosting. An example is mingw32.

To crossbuild GNU Pascal, you have to install a cross-compiler for your target first, see section Building and Installing a cross-compiler.

As when building a cross-compiler, configuration and compilation of the compiler can be done using the scripts `cfgpc' and `mkgpc' which are included in the source distribution in the subdirectory `p/script'. Please call them with the `-h' option for instructions.

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