#
# CDDL HEADER START
#
# The contents of this file are subject to the terms of the
# Common Development and Distribution License (the "License").
# You may not use this file except in compliance with the License.
#
# You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE
# See the License for the specific language governing permissions
# and limitations under the License.
#
# When distributing Covered Code, include this CDDL HEADER in each
# file and include the License file at usr/src/OPENSOLARIS.LICENSE.
# If applicable, add the following below this CDDL HEADER, with the
# fields enclosed by brackets "[]" replaced with your own identifying
# information: Portions Copyright [yyyy] [name of copyright owner]
#
# CDDL HEADER END
#
#
#
# There are a large number of macros in the GCB code written
# specifically for GCC's preprocessor. Studio does not expand
# these macros the same way GCC does, and the resulting gdb is
# not usable. Building gdb with a GCC >= 4.7.2 produces very
# good results, even on SPARC.
# The traditional output from gmake test omits some
# test results information that is contained in the
# for test results comparison.
# Results output is different on Intel vs. SPARC.
# Note that comparisons against master results
# are not clean since results will still vary.
# Test transforms retain only relevant results output.
'-n ' \
'-e "/^FAIL/p" ' \
'-e "/^KFAIL/p" ' \
'-e "/^PASS/p" ' \
'-e "/^UNRESOLVED/p" ' \
'-e "/^UNSUPPORTED/p" ' \
'-e "/^UNTESTED/p" ' \
'-e "/^XFAIL/p" ' \
'-e "/^\# of /p" '
# Test results vary from run to run and machine to machine,
# so master test results will not match, and are not
# appropriate for a full Userland test run
# GDB wants the GNU utilities
# Specify the C Standard to use when building
# Generate the newly added Solaris instruction and
# register tables which weren't there by default.
# Ensure PATH is set during build;
# pod2man perl script, used to create manpages
# build the manpages
# Disable ASLR: it's a debugger and we do not want to risk
# altering the results of the debugging experiment.