🚀 go-pugleaf

Archive-name: auto/comp.os.os2.programmer/GCC-2-2-2-2-now-available


I have just uploaded GCC/2 version 2.2.2 onto ftp-os2.nmsu.edu. It is
in pub/downloads/gcc2-2.2.2. The readme file is as follows:

-----

This is GCC/2 version 2.2.2.

What you need to compile things:

	gccbin.zoo - All executables
	gcchdr.zoo - Header files 
	gcclib.zoo - Libraries

Documentation:

	gccdoc.zoo - Texinfo sources of GCC manuals
	libman.zoo - Man pages for libc functions

Source code:

	libsrc.zoo - Source for libc and other stuff
	samples.zoo - Sample programs
	utilsrc.zoo - Sources for o2obj & stuff

If you are updrading from GCC/2 2.1 you only need to get gccbin.zoo
and gcclib.zoo.

-------

I am still cleaning up the source code for the compiler and hope to
have it up in a few days. The gccsrc* files that are in pub/downloads
are the old 2.1 sources.

There also a new version of libc.lib in gcclib.zoo. Only one thing has
changed; open.c now handles read-only files correctly so cpp won't
choke if you try and compile files set to +r.

The only changes to the header files are the corrected version of
pmwin.h that was posted a long time ago and process.h now declares
spawnv and spawnvp (these were needed to get GCC to link)

Thanks to Paul Lyon for your help and thoughts too.

Other things that need doing (ordered according to my priorities) :

	1. Create a PD librarian. It would seem the Toolkit doesn't
	   have LIB.EXE. This is strange as my beta toolkit did. My
	   production toolkit is still on order.

	2. Consider what to do with o2obj. I have 4 possible options:
	   		
		a) Leave it alone.
		b) Get it to convert debug info into a form LINK386
		   can use.
		c) Incorporate it into gas including debug info.
		d) Throw it away and port ld to create EXE's so that
		   LINK386 is no longer needed.

	   a) and b) don't really appeal to me. c) is probably the easiest
	   way to go, d) seems too much like reinventing the wheel.

	3. Go through the libraries and see what needs fixing. 

	4. Write a PD debugger. I may start with GDB but I haven't
	   looked at the sources yet.

	5. Write a proper configuration script to allow GCC to be
	   recompiled as a cross-compiler.

Feel free to email me if you have anything to add to this list, want
to plead for a change of priorities or (gasp) want to help with the
work.

-----
Trevor Lampre <mmtl@cc.flinders.edu.au>
Flinders University of South Australia