This is the port of gcc-3.2.1 for DJGPP.


Please read this file up to end (maybe skipping sections You don't need,
for example You don't need to read how to build gcc-3.2.1 from sources
if You only intend to use binary archives). Also consult DJGPP documentation
and FAQ where needed.


Requirements to use this binary release:
    Latest update of DJGPP-2.03 or above (If You are still using earlier version 
            then please upgrade immediatelly).
    binutils-2.13 or above recommended. Does not work with binutils older
	    than 2.11.2 any more.

Requirements to build gcc-3.2.1 from sources:
    Long filename support. I built it in DOS session under Win95.
    at least 128Mb of RAM for building under Win9X (Amount of available
        DPMI memory for DOS session should be set to auto). 
    at least DJGPP-2.03 required (Make sure You have latest update in this
        case).
    other GNU utilities (see below)


Source archives
===============

Archive gcc321s2.zip contains script which modifies original gcc-3.2.1
and sources for DJGPP. You don't need it unless You want to recreate
GCC source archive for DJGPP. If You are using this archive and original 
sources of gcc-3.2.1.tar.gz, then You don't need gcc321s.zip.
    
The source archive gcc321s.zip contains all the sources to build
all compilers (C, C++, Objective C, GNU Fortran) and also C++
and Fortran libraries (libstdcxx.a, libgpp.a and libg2c.a). 
libg++ is no more supported.

Most users don't need source archives at all.

Binary archives
================

Binary archives are split into 5 parts:

  gcc321b.zip   : The gcc.exe driver program and the C compiler.
                 It also contains the documentation.

  gpp321b.zip   : The C++ compiler and libstdcxx.a together 
                 with needed header files. Please note that one must
		 recompile all C++ sources built with any earlier GCC version

  objc321b.zip  : The Objective C compiler and libobjc.a and the needed
                 header files.

  g77321b.zip   : GNU Fortran compiler and libg2c.a and g2f.h. 

  ada321b.zip   : ADA compiler (untested)


The archive gcc321b.zip is required by all other binary packages

Binary packages includes following documentation files:
  
  Archive gcc321b.zip:  
	info/gcc.i* - the use and the internals of the GNU compiler
	info/cpp.i* - documentation of the GNU C preprocessor.
	info/cppinternals.i*  - internals of the GNU C Preprocessor.
		(NEW: use install-info to add it to info/dir)
  Archive gpp321b.zip:
        gnu/gcc-3.21/libstdcxx/* - some documentation of libstdc++-v3
		(HTML and text formats)
  Archive g77321b.zip:
	info/g77.i* - documentation of the GNU Fortran compiler


Before you install gcc-3.2.1 binaries
======================================

You should remove previous installation of gcc or egcs completely
(unless You really know what You are doing).

Make sure You don't have following files from earlier versions
(relative paths againt to DJGPP directory are given):
	bin/cc1.exe		(from gcc272b.zip or gcc2721b.zip)
	bin/cc1plus.exe		(from gpp272b.zip or gpp2721b.zip)
	bin/f771.exe		(from g7705XXb.zip, XX are 2 digits)
	lib/libgcc.a		(from gcc272b.zip or gcc2721b.zip)
	lib/libobjc.a		
	lib/specs		(from djdev201.zip or djdev202.zip) 
	lib/libstdcxx.a		
	lib/libgpp.a		

Following packages are required for binaries:
	binutils-2.13 or above is recommended, but possibly versions
	beginning with 2.11.2 will work (I have not tested that).

	Last update of DJGPP-2.03 (djdev203.zip) or above (earlier versions
	of djgpp203.zip are not compatible with gcc-3.2.1)


Installing binaries of gcc-3.2.1
=================================

Needed archives for different programing languages
	C 			: gcc321b.zip

	C++			: gcc321b.zip, gpp321b.zip

	Fortran	                : gcc321b.zip, g77321b.zip

	Objective C		: gcc321b.zip, objc321b.zip

	ADA			: gcc321b.zip, ada321b.zip

Of course for ALL languages You also need at least binutils (bnu2112b.zip
or newer) and djdev203.zip (or newer when it will be released)

Unzip all the zip files from that directory, preserving the
directory structure.  For example:

	pkunzip -d djdev203
or
	unzip386 djdev203


NOTE:   For debugging GDB version 5.2 or above is needed. Newer updates
	of RHIDE from http://rhide.sourceforge.net/snapshots is built
	with GDB-5.2.1 or better, so could be used to debug applications
	built with GCC-3.2.1. However even GDB-5.2.1 doesn't seem to work 
	with ADA programs.

NOTE:   I have changed to DWARF2 debugging info as the default. As result
	one will get DWARF2 debugging info when option -g will be specified. 
	One still can get COFF debugging info by using option -gcoff instead
	of -g. Similary one can use -gstabs or -gstabs+ to get stabs debugging
	info. Note that symify.exe from djdev20X.zip works with COFF debugging 
	info only. One can use bfdsymify.exe (see GDB binary archive)
	with DWARF2 or stabs debugging info. However bfdsymify must be
	linked with fresh enough BFD library (one from gdb511b.zip is too old)
	

1. Only long filenames
----------------------

Unzip the binaries with an unzip program, which can restore the long filenames
stored in the zip archive.

2. Only short filenames
-----------------------

Unzip the binaries with an unzip program which doesn't know about long
filenames, or if your unzipper knows about them, please follow first
the steps described in the DJGPP FAQ in the section 
about setting the NameNumericTail to 0 __BEFORE__!!! unzipping the archives.

3. Long and short filenames at the same time
--------------------------------------------

Use an unzip program which can restore the long filenames and follow
the instructions under 2. when the unzipper knows about long filenames.


Note for users of C++ IO classes fstream, ifstream, ofstream
============================================================

There is a regression against earlier versions of GCC (gcc-2.95.3 and
earlier): Member functions tellp(), tellg(), seekp() and seekg()
are broken when stream is opened not in binary mode. If You are going
to use any similar functions You should open stream in binary mode.

Don't ask me when it will be fixed as I don't know that. I'm also 
not sure I'll spend much time trying to fix that.


Rebuilding gcc-3.2.1 from the sources
======================================

Requirememts
------------

-  Long filename support is required. It means You should build gcc-3.2.1
   under Win95 or Win98. I myself have not tested building under Win2k 
   and WinXP

-  Much of free disk space (500Mb or more, especially if
   You are using FAT16). 

-  128Mb RAM (or more) to build gcc-3.2.1 under Win9X. DPMI memory amount 
   for DOS session should be set to "Auto" as genattrtab requires more 
   than 64Mb to run.	

-  Many GNU packges. Please check whether You really have them:
	bsh204b.zip 	GNU BASH 2.0.4 or above. 
	dif272b.zip
	fil316b.zip or newer (use of fil41b.zip is not recommended,
                              I had problems with it, fil40b.zip from Simtel
			      seems to be ok).
	find41b.zip
	grep24b.zip
	gwk306b.zip or newer
	mak3791b.zip
	sed302b.zip or newer
	shl112b.zip
	txt122b.zip or newer
	txi42b.zip or above (You will not get info files with older versions)
	tar112b.zip
	bnu213b.zip or above (perhaps also binutils-2.11.2 or above could work)
	working GNU C compiler (perhaps not earlier than gcc-2.8). 

   If You modify some source files You may also need
	acnf213b.zip (autoconf-2.50 should not be used)
	amak14b.zip or amak15b.zip
	
   You need autoconf and automake also if You are using gcc321s2.zip.
   However it's normally not needed for most users who builds gcc-3.2.1 from
   contents of gcc321s.zip.

   Usually newer versions of these packages should also work unless
   otherwise stated above

-  INFO-ZIP binary (compiled with DJGPP v2!!!) is needed for using build.sh 
   to create binary distrubution archives. There is no problems to compile 
   it. See http://www.info-zip.org for additional informtion
   about INFO-ZIP. You can find DJGPP compiled binary there. 

-  Working DJGPP installation of course:
	DJGPP-2.03 and above (Please verify that You really have current 
                update of djdev203.zip if You use 2.03). 
   	2.13 or above recommended (perhaps 2.11.2 or above works)
	working gcc installation (perhaps gcc-2.95 or above)

-  You should have sh.exe in DJGPP bin directory as symbolic link to  
   bash.exe (type 'ln -s bash.exe sh.exe' in that directory)


Extracting the sources
----------------------

At first you should unzip the archive gcc321s.zip. The sources are _NOT_
the complete sources like the original gcc-3.2.1 distribution. I have
removed many files to save disk space which are not needed for the DJGPP
port. However I left configuration of other machines in to make archives
usable to build cross-to-DJGPP compilers


Compiling gcc
-------------

Directory gnu/gcc-3.2.1 contains all sources of gcc-3.2.1

Sources are NOT configured. 
	
Change to directory gnu/build.gcc and configure sources
by running script djconfig.sh. 

	sh djconfig.sh

When this is done You can build gcc-3.2.1 by running script djmake.sh
Under Win9X You'll have to restart it some times when it will crash 
due to Win9X DPMI descriptor leaks. You may use redir to get output in file.

	sh djmake.sh bootstrap

After that build ADA tools and libraries (if ADA support is being built):

	sh djmake.sh -C gcc gnatlib_and_tools

When this sucessfully ends run script djinsttmp.sh which installs
all into directory gnu/install.gcc

After that change to this directory and run script makepkg.sh
to create binary distribution packages
	

Installing newly compiled gcc
-----------------------------

It's recommended to install binary packages which are generated 
by makepkg.sh



Available resources
===================

See following URL for additional information:
gcc:		  http://gcc.gnu.org



Reporting bugs
==============

If you found a bug in gcc-3.2.1 (gcc, g77, libstdc++, etc) please report it to 
the GCC bug adresses and _NOT_ (or at least not only) in the DJGPP news group. 

But if you think you found a bug in the DJGPP related things, then please 
report it in comp.os.msdos.djgpp (the news group) or mail it to 
djgpp@delorie.com, which is the gateway to the news group.

Some possible situations:
  - gcc says 'Internal compiler error' (or something similar)
       more likely it is error of gcc if it is reproducible. It would 
       be nice to test on some other system (e.g. Linux) and also with 
       different version of compiler if possible and submit report to 
       gcc bug address. 
  - gcc crashes or freezes. 
       In this situation it's hard to guess where is the problem. It may be
       problem with gcc itself but it may be also DJGPP specific one.

Please email me directly only in rare cases, if you think it is only of
interest to me, since I'll see the reports in DJGPP mailing list.


Thanks to
=========

To all who have contributed new features, test results, bugfixes to GCC
(see http://gcc.gnu.org/thanks.html) and also who helped with DJGPP port of 
gcc-3.2.1


Have fun with gcc

Andris Pavenis <pavenis@lanet.lv>

