The sandbox ($SB)

The build instructions have been greatly simplified by using the sandbox model from OSF. A sandbox is just a tree which has a file .sandbox-env at the top, which serves to both mark the top of the tree and provide a means of conditioning the environment.

The tools described below are all in sb-tools

exec ${REAL_MAKE:-${MAKE:-make}} "$@"

exec-shell.sh shell=/bin/ksh mk

#!/bin/sh
script=`echo $0 | sed 's,sunos/,,'`
exec /usr/xpg4/bin/sh $script "$@"

bmake

Unless you are running a recent NetBSD, you must build bmake which is a portable version of NetBSD's make and tracks it closely (I am one of the maintainers of NetBSD make since the late '90s).

This tree is designed to be built with bmake and with support for multiple architectures. GNU autoconf is used to generate a config.h which handles most system dependencies, but the Makefiles rely on bmake. Fortunately bmake uses autoconf :-)

Bmake has a lot of other advantages over GNU make, like META_MODE My .sandboxrc has:

export WITH_DIRDEPS_BUILD=yes
export WITH_META_MODE=yes
export WITH_DPADD_MK=yes
export WITH_AUTO_OBJ=yes
export WITH_STAGING=yes

The DIRDEPS_BUILD takes advantage of the Makefile.depend files found in each src directory - to know the correct order in which to build the whole tree in parallel. Ok that's more impressive in a big project like the FreeBSD tree (see FreeBSD META_MODE).

$ tar zxf ~/bmake.tar.gz
$ ./bmake/boot-strap

$ tar zxf ~/bmake.tar.gz
$ cd bmake
$ ./configure
$ make
$ make install

:
echo "Building for $HOST_TARGET"
case "$HOST_TARGET" in
netbsd*) sys_share_mk=:/usr/share/mk;;
sunos*) sys_share_mk=
        CC=`type gcc | sed 's,^[^/]*,,'`
        export CC
        ;;
*)      sys_share_mk=;;
esac
objdir=./$HOST_TARGET
case "$prefix" in
*/$HOST_TARGET)
        CONFIGURE_ARGS="$CONFIGURE_ARGS --with-default-sys-path=$prefix/share/mk:`dirname $prefix`/share/mk$sys_share_mk"
        ;;
esac

Makefiles

The Makefiles want to know where the top level directory is. The easy way to do this is with the mk wrapper mentioned above.

These Makefiles use my own macro files which were originally derived from the NetBSD (1.0?) bsd.*.mk macros. You can put them where ever you like and set the location in $MAKESYSPATH in $SB/.sandbox-env. The default location is $SB/mk

We default the macro MK_MAN=no to suppress formatting of man pages. You can override this if you have the BSD mandoc macros for [nt]roff.

Macro files

A couple of my macro files differ from the bsd.* originals (apart from being more portable), man.mk handles installing unformatted nroff, as well as formatted pages with the normal extension rather than BSD's .0

Unless SUBDIR_MUST_EXIST is defined, subdir.mk will skip missing subdirs (after telling you...) rather than die. This is important, since you very likely have a subset of the full src tree.

Building

In various directories, you may find symlinks named src pointing off to no where. These should point to the directories holding the appropriate distribution. For instance:

$ ls -l ssl/bin/rdist/src
lrwxrwxr-x  1 sjg  wheel  17 Jun 20  1996 ssl/bin/rdist/src@ -> ../../../../rdist-6.1.3
$

Obviously you will need these links correct before you can expect to build things like SSLrdist. See other distributions for details on where to get the other distributions you might need.

Now just:

$ PATH=$PATH:$SB/scripts
$ cd $SB
$ mk
# mk install

# gcc, but an old version
USE_AUTODEP_MK=no
USE_DMALLOC?=no
USE_DBUG?=no
USE_DPADD_MK=yes
WARNINGS_SET?=MIN

SB_SRC=$SB
SB_NAME=`basename $SB`
SRCTOP=$SB
OBJTOP=${MAKEOBJDIRPREFIX:-/var/obj/$SB_NAME}
MAKEOBJDIR='${.CURDIR:S,${SRCTOP},${OBJTOP},}'
MKOBJDIRS=auto
MAKECONF=$SB/Makefile.inc
MAKESYSPATH=$SB/mk
if [ -s /netbsd ]; then
        BMAKE=${BMAKE:-make}
else
        BMAKE=${BMAKE:-$HOME/$HOST_TARGET/bin/bmake}
fi
REAL_MAKE=${BMAKE:-bmake}
# we only need these if using the full mk version.
SB_PROJECT=sjg
SB_PATH=${PATH:-/usr/bin:/bin:/usr/sbin:/sbin:/usr/pkg/bin:/usr/local/bin}
# on many "modern" systems /bin/sh is not posix compliant
# so we avoid export VAR=value
unset  MAKEOBJDIRPREFIX
export SB_SRC SB_NAME
export SRCTOP OBJTOP
export MAKESYSPATH MAKECONF MAKEOBJDIR
export MKOBJDIRS
export REAL_MAKE

# ln -s /usr/local/lib/libsslfd.so.0.3 /usr/local/lib/libsslfd.so.0

# ln -s libsslfd.so.0.3 libsslfd.so

SSL

The ssl tree here now expects OpenSSL to be already installed, it will try to guess where but you may need to set INCLUDES_libcrypto in local.libnames.mk

Example

An example usually helps. The following assumes that OpenSSL has been built and installed.

First unpack all the packages in a single tree such as ~/work/sjg (this will be $SB):

$ mkdir -p ~/work/sjg
$ cd ~/work/sjg
$ gzcat /tmp/bmake.tar.gz | tar xvf -
$ gzcat /tmp/mk.tar.gz | tar xvf -
$ gzcat /tmp/SSLrsh.tar.gz | tar xvf -
..
..

Note: if you have already installed bmake you do not need to unpack it in $SB.

Also note that if you want to support sharing read-only src via NFS ensure that .sandbox-env sets OBJTOP=/var/obj/$SB_NAME or similar.

You will likely need to be root to install anything as the install macros use chown which is usually restricted to root:

# mk install

If you want to force installing without chown etc:

$ mk install BINOWN= LIBOWN=

breakage

It is highly likely that your source tree is a small subset of ours. We have taken steps to try and ensure that the build will work for you despite this, but we may have missed something.

It is also possible (likely) that newer OS versions can introduce new hiccups - especially since much of the code in telnet for example is pretty old.

In general it is safest to start with a clean tree. If you have unpacked previous versions of SSLrsh.tar you may have Makefiles or headers present that are not in the current release and will cause you problems.