Makefile revision 2833
4910N/A# The contents of this file are subject to the terms of the 4910N/A# Common Development and Distribution License (the "License"). 4910N/A# You may not use this file except in compliance with the License. 4910N/A# See the License for the specific language governing permissions 4910N/A# and limitations under the License. 4910N/A# When distributing Covered Code, include this CDDL HEADER in each 4910N/A# If applicable, add the following below this CDDL HEADER, with the 4910N/A# fields enclosed by brackets "[]" replaced with your own identifying 4910N/A# information: Portions Copyright [yyyy] [name of copyright owner] 4910N/A# Copyright (c) 2011, 2014, Oracle and/or its affiliates. All rights reserved. 4910N/A# Need to preserve timestamp for Grammar files. If the pickle files are older, 4910N/A# Python will try to rebuild them. 4910N/A# We patch auto* files, so regenerate headers and configure 4976N/A# we don't want to leak $(CC_BITS) into BASECFLAGS as it causes problems with 4910N/A# to find the ncurses headers 4910N/A# enable large files how they did in JDS 4910N/A# because python links with $(CC) ... $(LDFLAGS) ... 4910N/A# The python build is profile-guided for studio; to see the benefits of that, 4910N/A# Python must be compiled with -xO5 and a different build target must be used. 4910N/A# Use of xprofile requires that the same options be used during compilation and 4910N/A# linking. The targets chosen are based on Solaris 11 minimum supported system 4910N/A# Python puts its header files in a special place. 4910N/A# 64 bit shared objects need to go in a 64-bit directory 4910N/A# *.txt files in the same directory, it will rebuild them anytime you try to 4910N/A# build a Python module. So here we also touch the pickle files to avoid this. 4910N/A# Using "-uall,-network" ensures all tests are run except the network tests. 4910N/A# The network tests contain many expected failures when run behind a firewall. 4910N/A# The "-v" ensures verbose mode. You can set TESTOPTS_PYTHON_TEST to a 4910N/A# particular test if you want to run just one test. For example, run gmake with 4910N/A# "-k" so it continues and does both 32-bit and 64-bit tests, even if there is a 4910N/A# $ TESTOPTS_PYTHON_TEST=test_sys gmake -k test 4910N/A# Note that when a test succeeds, the builds/*/.tested file gets created. You 4910N/A# may need to remove these files, or run "gmake clobber" or "gmake clean"