-################################################################################
-
-# The configuration is defined in two steps:
-#
-# 1. The builder (i.e. the person doing the build)
-# copies this file, config.mk.in-template
-# to config.mk.in
-#
-# 2. S/he then edits it manually (gasp) to reflect any configuration
-# options s/he wants.
-#
-# 3. Then s/he runs "configure", which generates config.mk from
-# config.mk.in, substituting for system/platform-dependent things
-# enclosed in @at-signs@.
-#
-# This is one of only two files that configure generates (the other is config.h)
-#
-# Note that after subsequent edits of config.mk.in for a build, the configure script
-# will have to be re-run manually to have the change reflected in config.mk.
-#
-
-# There is a section below for each project within the fptools suite
-#
-# PLUS
-#
-# a section corresponding to each of the main .mk files
-# included by boilerplate.mk (see boilerplate.mk for a list).
-
-
-################################################################################
-#
-# Project-wide platform variables
-#
-################################################################################
-
-# A "platform" is the GNU cpu-type/manufacturer/operating-system target machine
-# specifier. E.g. sparc-sun-solaris2
-
-HOSTPLATFORM = @HostPlatform@
-TARGETPLATFORM = @TargetPlatform@
-BUILDPLATFORM = @HostPlatform@
-
-# Hack alert:
-# in one or two places, we need to get at the OS version (major and perhaps even minor),
-# HostOS_Full is the OS name reported by AC_CANONICAL_SYSTEM.
-#
-HostPlatform_CPP = @HostPlatform_CPP@
-HostArch_CPP = @HostArch_CPP@
-HostOS_CPP = @HostOS_CPP@
-HostOS_Full = @HostOS_Full@
-HostVendor_CPP = @HostVendor_CPP@
-