RE: State of TOOLSRC?

> (1) the toplevel configure.ac has a hand-crafted macro that 
> bails out if
> C++ sizeof bool != 1. This is pretty unportable (sample: 
> NetBSD/sparc - 4,
> NetBSD/macppc - 4, Apple MacOS X - 4) to probably any RISC cpu.
> If you need sizeof bool == sizeof char, you probably 
> shouldn't use bool in
> that place, anyway.

The first compiler where there were actual problems was gcc 3.1 for IA64 and they mended their ways. Compilers for Solaris, AIX, HP-UX and DecUnix all use sizeof (bool) == 1, otherwise, we would have fixed that long ago. It looks as if we have to anyway. Although, if I remember right, the places
that need fixing are far from obvious.

> So, TOOLSRC looks like it could use some work. Has the cvs 
> source state
> ever built? Has it built on any cpu besides i386? On any OS 
> besides a linux

It's been build some time ago on Solaris/Sparc and AIX and others have been able to build them on Solaris/I386 and Linux/s390. But it certainly could use some work, especially as there are still platform tests all over the place.

We could also use a lot of help on enabling autoconf for the rest of the software.

> the sapdb project? Where can I send patches, how should they 
> be set up, how

I will send a separate mail to this list.

> can I get an idea of overall structure?

TOOLSRC only:
sys/src/base contains everything that is created by Makefiles and is needed to bootstrap the development environment. A few Perl-Scripts are needed as well and they a copied in basescripts.mk.

The rest of the tools is build by calling the SAP DB make tool vmake:
in Makefile.in
#
# runs vmake to create remaining tools
#
alltools:
        $(BUILDDIR)/envexec $(BUILDDIR) $(TOOL) perl $(TOOL)/bin/imf.pl -i alltools

Daniel Dittmar

-- 
Daniel Dittmar
SAP DB, SAP Labs Berlin
[email protected]
http://www.sapdb.org/