Makefile revision 3722
2818N/A# The contents of this file are subject to the terms of the 2818N/A# Common Development and Distribution License (the "License"). 2818N/A# You may not use this file except in compliance with the License. 2818N/A# See the License for the specific language governing permissions 2818N/A# and limitations under the License. 2818N/A# When distributing Covered Code, include this CDDL HEADER in each 2818N/A# If applicable, add the following below this CDDL HEADER, with the 2818N/A# fields enclosed by brackets "[]" replaced with your own identifying 2818N/A# information: Portions Copyright [yyyy] [name of copyright owner] 2818N/A# Copyright (c) 2011, 2015, Oracle and/or its affiliates. All rights reserved. 2818N/A# Need to preserve timestamp for Grammar files. If the pickle files are older, 2818N/A# Python will try to rebuild them. 2818N/A# We patch auto* files, so regenerate headers and configure 2818N/A# we don't want to leak $(CC_BITS) into BASECFLAGS as it causes problems with 2818N/A# to find the ncurses headers 2818N/A# enable large files how they did in JDS 2818N/A# because python links with $(CC) ... $(LDFLAGS) ... 2818N/A# The python build is profile-guided for studio; to see the benefits of that, 2818N/A# Python must be compiled with -xO5 and a different build target must be used. 2818N/A# Use of xprofile requires that the same options be used during compilation and 4302N/A# linking. The targets chosen are based on Solaris 11 minimum supported system 2818N/A# Python puts its header files in a special place. 2818N/A# PYTHONPATH in the environment can be harmful, but setting it to empty via 2818N/A# _INSTALL_ENV causes problems too, so just ignore the entire environment. 2818N/A# Because of this, we need to specify PATH in multiple places below. 2818N/A# 64 bit shared objects need to go in a 64-bit directory 2818N/A# Simplify the definitions of CC, CXX, CFLAGS and LDFLAGS so they hard-code 2818N/A# neither paths from our build systems nor Studio-specific options. 3693N/A (cd $(@D) ; $(GSED) -i -e 's/^CC=.*/CC=\t\tcc/' \ 2818N/A -e 's/^CXX=.*/CXX=\t\tCC/' \ 2818N/A -e 's/^CFLAGS=.*/CFLAGS=\t\t\$$\(BASECFLAGS) \$$\(OPT) \$$\(EXTRA_CFLAGS)/' \ 2818N/A -e 's|^LDFLAGS=.*|LDFLAGS=|' \ 2818N/A# Because we stripped the Makefile above, we need to pass several things in the 2818N/A# environment, and use -e to tell gmake to pay attention to the environment. 3497N/A# related *.txt files in the same directory, it will rebuild them any time 3497N/A# you try to build a Python module. So here we also touch the pickle files 3497N/A# Note that although the 64-bit version is not used (and thus commented 3497N/A# out in the manifest), we still need to specify the 32-/64-bit paths, 3497N/A# otherwise the 64-bit build will fail to find the 32-bit path. 3497N/A $(GSED) -i -e 's|$(SOURCE_DIR)|.|g' -e 's|$(COMPONENT_DIR)|..|g' \ 2818N/A# Using "-uall,-network" ensures all tests are run except the network tests. 2818N/A# The network tests contain many expected failures when run behind a firewall. 2818N/A# The "-v" ensures verbose mode. You can set TESTOPTS_PYTHON_TEST to a 2818N/A# particular test if you want to run just one test. For example, run gmake with 2818N/A# "-k" so it continues and does both 32-bit and 64-bit tests, even if there is a 2818N/A# $ TESTOPTS_PYTHON_TEST=test_sys gmake -k test 2818N/A# Note that when a test succeeds, the builds/*/.tested file gets created. You 2818N/A# may need to remove these files, or run "gmake clobber" or "gmake clean" 2818N/A# The distutils tests need $CC in $PATH.