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