cpet/openbsd-ports
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
a540a8b3b4
openbsd-ports/lang/python/Makefile.inc

141 lines
4.9 KiB
PHP
Raw Normal View History

Allow Python to build on loongson. Bring in some libffi fixes, inspired by jasper@'s fixes to the libffi port. Mark mips64 (aka, sgi) as BROKEN, as the build fails. We'll look closer at this after unlock. OK jasper@ ports is unlocked for a while only for those who have been informed.
2010-02-25 06:02:39 -05:00
# $OpenBSD: Makefile.inc,v 1.64 2010/02/25 11:02:39 phessler Exp $
- 2.2 -> 2.2.1 - annotate patches submitted to Python patch tracker - 100% license compliance: install CHANGES.OpenBSD file
2002-05-11 17:35:13 -04:00
# IMPORTANT! If you make any changes to the Python ports, be sure
# to also update files/CHANGES.OpenBSD for your change. This is a
# requirement of the PSF license, if it constitutes a change to
# Python itself.
Python 2.1.2 and Python 2.2. Major changes: - no more threads flavor, threads is now the default. - subpackage modules that depend on other packages instead of having largely redundant flavors (unless platform has no shared libs, then flavors count again) - shared libpython stuff disabled until someone can figure out why it makes Zope crash
2002-02-15 14:42:18 -05:00
SHARED_ONLY, part one
2006-10-10 15:08:06 -04:00
SHARED_ONLY= Yes
Remove surrounding quotes in COMMENT*/PERMIT_*/BROKEN
2007-09-15 20:27:05 -04:00
COMMENT-main= interpreted object-oriented programming language
COMMENT-bsddb= Berkeley db module for Python
COMMENT-gdbm= GNU dbm module for Python
COMMENT-idle= IDE for Python
COMMENT-tests= Python test suite
COMMENT-tkinter=tk GUI module for Python
COMMENT-tools= extra tools for Python
Python 2.1.2 and Python 2.2. Major changes: - no more threads flavor, threads is now the default. - subpackage modules that depend on other packages instead of having largely redundant flavors (unless platform has no shared libs, then flavors count again) - shared libpython stuff disabled until someone can figure out why it makes Zope crash
2002-02-15 14:42:18 -05:00
new MULTI_PACKAGES
2006-11-24 15:48:23 -05:00
PKGNAME-main= python-${VERSION}${PATCHLEVEL}${PKG_PATCHLEVEL}
Python 2.1.2 and Python 2.2. Major changes: - no more threads flavor, threads is now the default. - subpackage modules that depend on other packages instead of having largely redundant flavors (unless platform has no shared libs, then flavors count again) - shared libpython stuff disabled until someone can figure out why it makes Zope crash
2002-02-15 14:42:18 -05:00
DISTNAME= Python-${VERSION}${PATCHLEVEL}
CATEGORIES= lang
Fix MASTER_SITES
2005-11-11 04:45:29 -05:00
MASTER_SITES= http://www.python.org/ftp/${PSUBDIR}/ \
http://python.mirrors.pair.com/pub/${PSUBDIR}/
python-2.5.2 tested with a full ports build by naddy@ ok pvalchev@
2008-02-26 19:30:47 -05:00
PSUBDIR?= python/${VERSION}${PATCHLEVEL}
Python 2.1.2 and Python 2.2. Major changes: - no more threads flavor, threads is now the default. - subpackage modules that depend on other packages instead of having largely redundant flavors (unless platform has no shared libs, then flavors count again) - shared libpython stuff disabled until someone can figure out why it makes Zope crash
2002-02-15 14:42:18 -05:00
EXTRACT_SUFX= .tgz
HOMEPAGE= http://www.python.org/
Prepare for Python-2.6 Flip default ALL_TARGET to the one that will be used for current and future (>=2.5) Python releases, move old default down into 2.3 and 2.4 Makefiles Turn on a verbose retry when regress tests fail; saves messing with LD_LIBRARY_PATH incantations to get them to rerun Take maintainership
2008-10-18 07:55:57 -04:00
MAINTAINER= Damien Miller <djm@openbsd.org>
new packages -gdbm (GNU DBM support) and -idle (split from -tools) from new maintainer Aleksander Piotrowski <aleksander dot piotrowski at nic dot com dot pl> more to come
2003-12-13 10:03:07 -05:00
- 2.2 -> 2.2.1 - annotate patches submitted to Python patch tracker - 100% license compliance: install CHANGES.OpenBSD file
2002-05-11 17:35:13 -04:00
# PSF license <http://www.python.org/${VERSION}/license.html>
# A summary of changes to Python is required to be distributed
Python 2.1.2 and Python 2.2. Major changes: - no more threads flavor, threads is now the default. - subpackage modules that depend on other packages instead of having largely redundant flavors (unless platform has no shared libs, then flavors count again) - shared libpython stuff disabled until someone can figure out why it makes Zope crash
2002-02-15 14:42:18 -05:00
PERMIT_PACKAGE_CDROM= Yes
PERMIT_PACKAGE_FTP= Yes
PERMIT_DISTFILES_CDROM= Yes
PERMIT_DISTFILES_FTP= Yes
Updates and garbage collect all three Python ports: 2.4.4 => 2.4.8 2.5.2 => 2.5.4 2.6 => 2.6.1 Python 2.4 and 2.5 lose their build knobs to match 2.6. Removes no longer needed Python 2.5 security patches backported from the release25-maint SVN branch. Remove the -bz2 subpackage from all three versions. It is silly to make a subpackage to avoid depending on something tiny and compatibly licensed. Python 2.4 and 2.5 lose their -expat subpackages; expat has been in base for some time. Python 2.5 loses its sqlite subpackge. Again, sqlite is tiny, compatibly licensed and is depended upon by more and more applications. This brings it into line with the 2.6 version. Rework all three version's handling of setup.py. Rather than regex replacing LOCALBASE and X11BASE into setup.py post-configure, these are passed in though environment variables. Will save hours of frustrated cursing familiar to anyone who has accidently used the update-patches target after configure and had to go back and redo all the substitutions. Rework the patching of setup.py for 2.4 and 2.5 to be more like what we do for 2.6. I.e. keep the diff minimal and avoid deleting huge blocks of code, so the diff has a chance of applying without massive hand-editing each patch release. Fix .py paths in installed .pyc files (patch from eric@) feedback from several, particularly eric@, ajacoutot@ and Ingo Schwarze; "get it in" ajacoutot@
2009-01-01 16:03:27 -05:00
MULTI_PACKAGES= -main -tests -tools -gdbm -idle -tkinter
Prepare for Python-2.6 Flip default ALL_TARGET to the one that will be used for current and future (>=2.5) Python releases, move old default down into 2.3 and 2.4 Makefiles Turn on a verbose retry when regress tests fail; saves messing with LD_LIBRARY_PATH incantations to get them to rerun Take maintainership
2008-10-18 07:55:57 -04:00
Updates and garbage collect all three Python ports: 2.4.4 => 2.4.8 2.5.2 => 2.5.4 2.6 => 2.6.1 Python 2.4 and 2.5 lose their build knobs to match 2.6. Removes no longer needed Python 2.5 security patches backported from the release25-maint SVN branch. Remove the -bz2 subpackage from all three versions. It is silly to make a subpackage to avoid depending on something tiny and compatibly licensed. Python 2.4 and 2.5 lose their -expat subpackages; expat has been in base for some time. Python 2.5 loses its sqlite subpackge. Again, sqlite is tiny, compatibly licensed and is depended upon by more and more applications. This brings it into line with the 2.6 version. Rework all three version's handling of setup.py. Rather than regex replacing LOCALBASE and X11BASE into setup.py post-configure, these are passed in though environment variables. Will save hours of frustrated cursing familiar to anyone who has accidently used the update-patches target after configure and had to go back and redo all the substitutions. Rework the patching of setup.py for 2.4 and 2.5 to be more like what we do for 2.6. I.e. keep the diff minimal and avoid deleting huge blocks of code, so the diff has a chance of applying without massive hand-editing each patch release. Fix .py paths in installed .pyc files (patch from eric@) feedback from several, particularly eric@, ajacoutot@ and Ingo Schwarze; "get it in" ajacoutot@
2009-01-01 16:03:27 -05:00
# Python 2.6 lists BSD db 4.6.x as unstable on most architectures (see
# setup.py:allow_db_version). XXX revisit if databases/db/v4 is updated to 4.7
.if ${VERSION} != "2.6" || \
${MACHINE_ARCH} == "amd64" || ${MACHINE_ARCH} == "i386"
MULTI_PACKAGES+=-bsddb
.endif
Python 2.1.2 and Python 2.2. Major changes: - no more threads flavor, threads is now the default. - subpackage modules that depend on other packages instead of having largely redundant flavors (unless platform has no shared libs, then flavors count again) - shared libpython stuff disabled until someone can figure out why it makes Zope crash
2002-02-15 14:42:18 -05:00
fix dependencies - subpackage @pkgdep -> RUN_DEPENDS - no no_tkinter shouldn't unconditionally add LIB_DEPENDS of tk
2002-03-22 23:34:22 -05:00
# All subpackages depend on the main python package.
Updates and garbage collect all three Python ports: 2.4.4 => 2.4.8 2.5.2 => 2.5.4 2.6 => 2.6.1 Python 2.4 and 2.5 lose their build knobs to match 2.6. Removes no longer needed Python 2.5 security patches backported from the release25-maint SVN branch. Remove the -bz2 subpackage from all three versions. It is silly to make a subpackage to avoid depending on something tiny and compatibly licensed. Python 2.4 and 2.5 lose their -expat subpackages; expat has been in base for some time. Python 2.5 loses its sqlite subpackge. Again, sqlite is tiny, compatibly licensed and is depended upon by more and more applications. This brings it into line with the 2.6 version. Rework all three version's handling of setup.py. Rather than regex replacing LOCALBASE and X11BASE into setup.py post-configure, these are passed in though environment variables. Will save hours of frustrated cursing familiar to anyone who has accidently used the update-patches target after configure and had to go back and redo all the substitutions. Rework the patching of setup.py for 2.4 and 2.5 to be more like what we do for 2.6. I.e. keep the diff minimal and avoid deleting huge blocks of code, so the diff has a chance of applying without massive hand-editing each patch release. Fix .py paths in installed .pyc files (patch from eric@) feedback from several, particularly eric@, ajacoutot@ and Ingo Schwarze; "get it in" ajacoutot@
2009-01-01 16:03:27 -05:00
RUN_DEPENDS= :python-${VERSION}${PATCHLEVEL}${PKG_PATCHLEVEL}:lang/python/${VERSION},-main
Better dependencies for (sub)packages
2005-03-03 18:20:47 -05:00
LIB_DEPENDS=
new MULTI_PACKAGES
2006-11-24 15:48:23 -05:00
Updates and garbage collect all three Python ports: 2.4.4 => 2.4.8 2.5.2 => 2.5.4 2.6 => 2.6.1 Python 2.4 and 2.5 lose their build knobs to match 2.6. Removes no longer needed Python 2.5 security patches backported from the release25-maint SVN branch. Remove the -bz2 subpackage from all three versions. It is silly to make a subpackage to avoid depending on something tiny and compatibly licensed. Python 2.4 and 2.5 lose their -expat subpackages; expat has been in base for some time. Python 2.5 loses its sqlite subpackge. Again, sqlite is tiny, compatibly licensed and is depended upon by more and more applications. This brings it into line with the 2.6 version. Rework all three version's handling of setup.py. Rather than regex replacing LOCALBASE and X11BASE into setup.py post-configure, these are passed in though environment variables. Will save hours of frustrated cursing familiar to anyone who has accidently used the update-patches target after configure and had to go back and redo all the substitutions. Rework the patching of setup.py for 2.4 and 2.5 to be more like what we do for 2.6. I.e. keep the diff minimal and avoid deleting huge blocks of code, so the diff has a chance of applying without massive hand-editing each patch release. Fix .py paths in installed .pyc files (patch from eric@) feedback from several, particularly eric@, ajacoutot@ and Ingo Schwarze; "get it in" ajacoutot@
2009-01-01 16:03:27 -05:00
LIB_DEPENDS-main= bz2::archivers/bzip2
new MULTI_PACKAGES
2006-11-24 15:48:23 -05:00
RUN_DEPENDS-main=
Updates and garbage collect all three Python ports: 2.4.4 => 2.4.8 2.5.2 => 2.5.4 2.6 => 2.6.1 Python 2.4 and 2.5 lose their build knobs to match 2.6. Removes no longer needed Python 2.5 security patches backported from the release25-maint SVN branch. Remove the -bz2 subpackage from all three versions. It is silly to make a subpackage to avoid depending on something tiny and compatibly licensed. Python 2.4 and 2.5 lose their -expat subpackages; expat has been in base for some time. Python 2.5 loses its sqlite subpackge. Again, sqlite is tiny, compatibly licensed and is depended upon by more and more applications. This brings it into line with the 2.6 version. Rework all three version's handling of setup.py. Rather than regex replacing LOCALBASE and X11BASE into setup.py post-configure, these are passed in though environment variables. Will save hours of frustrated cursing familiar to anyone who has accidently used the update-patches target after configure and had to go back and redo all the substitutions. Rework the patching of setup.py for 2.4 and 2.5 to be more like what we do for 2.6. I.e. keep the diff minimal and avoid deleting huge blocks of code, so the diff has a chance of applying without massive hand-editing each patch release. Fix .py paths in installed .pyc files (patch from eric@) feedback from several, particularly eric@, ajacoutot@ and Ingo Schwarze; "get it in" ajacoutot@
2009-01-01 16:03:27 -05:00
WANTLIB-main= ssl panel m crypto c util z readline pthread \
ncurses stdc++ expat ossaudio
.if ${VERSION} == "2.5" || ${VERSION} == "2.6"
LIB_DEPENDS-main+= sqlite3::databases/sqlite3
Prepare for Python-2.6 Flip default ALL_TARGET to the one that will be used for current and future (>=2.5) Python releases, move old default down into 2.3 and 2.4 Makefiles Turn on a verbose retry when regress tests fail; saves messing with LD_LIBRARY_PATH incantations to get them to rerun Take maintainership
2008-10-18 07:55:57 -04:00
.endif
new MULTI_PACKAGES
2006-11-24 15:48:23 -05:00
a few spec fixes and assorted pkg bumps, more to come.
2009-03-09 19:09:19 -04:00
LIB_DEPENDS-bsddb= lib/db4/db.>=4:db->=4,<5:databases/db/v4
new MULTI_PACKAGES
2006-11-24 15:48:23 -05:00
LIB_DEPENDS-gdbm= gdbm.>=3::databases/gdbm
RUN_DEPENDS-idle= ${RUN_DEPENDS} \
::lang/python/${VERSION},-tkinter
a few spec fixes and assorted pkg bumps, more to come.
2009-03-09 19:09:19 -04:00
LIB_DEPENDS-tkinter= tcl84:tcl->=8.4,<8.5:lang/tcl/8.4 \
tk84:tk->=8.4,<8.5:x11/tk/8.4
WANTLIB changes after xcb addition and bump. For some unknown reason, I forgot to commit lang/* this morning.
2009-08-10 13:31:07 -04:00
WANTLIB-tkinter= X11 pthread-stubs xcb
Python 2.1.2 and Python 2.2. Major changes: - no more threads flavor, threads is now the default. - subpackage modules that depend on other packages instead of having largely redundant flavors (unless platform has no shared libs, then flavors count again) - shared libpython stuff disabled until someone can figure out why it makes Zope crash
2002-02-15 14:42:18 -05:00
- Move stuff around in preparation for python 2.4 - Better WANTLIB marker for base package
2005-05-23 16:39:36 -04:00
FULLPKGNAME-bsddb= python-bsddb-${VERSION}${PATCHLEVEL}${PKG_PATCHLEVEL}
new packages -gdbm (GNU DBM support) and -idle (split from -tools) from new maintainer Aleksander Piotrowski <aleksander dot piotrowski at nic dot com dot pl> more to come
2003-12-13 10:03:07 -05:00
FULLPKGNAME-gdbm= python-gdbm-${VERSION}${PATCHLEVEL}${PKG_PATCHLEVEL}
FULLPKGNAME-idle= python-idle-${VERSION}${PATCHLEVEL}${PKG_PATCHLEVEL}
FULLPKGNAME-tests= python-tests-${VERSION}${PATCHLEVEL}${PKG_PATCHLEVEL}
Fix security issue with Python 2.1/2.2 Zack Weinberg found a vulnerability in the way the exevpe() method from the os.py module uses a temporary file name. A file which supposedly should not exist is created in a unsafe way and the method tries to execute it. The objective of such code is to discover what error the operating system returns in a portable way. By exploiting this vulnerability a local attacker can execute arbitrary code with the privileges of the user running python code which uses the execvpe() method. http://python.org/sf/590294 http://python.org/sf/601077
2002-10-07 22:52:25 -04:00
FULLPKGNAME-tkinter= python-tkinter-${VERSION}${PATCHLEVEL}${PKG_PATCHLEVEL}
new packages -gdbm (GNU DBM support) and -idle (split from -tools) from new maintainer Aleksander Piotrowski <aleksander dot piotrowski at nic dot com dot pl> more to come
2003-12-13 10:03:07 -05:00
FULLPKGNAME-tools= python-tools-${VERSION}${PATCHLEVEL}${PKG_PATCHLEVEL}
Python 2.1.2 and Python 2.2. Major changes: - no more threads flavor, threads is now the default. - subpackage modules that depend on other packages instead of having largely redundant flavors (unless platform has no shared libs, then flavors count again) - shared libpython stuff disabled until someone can figure out why it makes Zope crash
2002-02-15 14:42:18 -05:00
Allow Python to build on loongson. Bring in some libffi fixes, inspired by jasper@'s fixes to the libffi port. Mark mips64 (aka, sgi) as BROKEN, as the build fails. We'll look closer at this after unlock. OK jasper@ ports is unlocked for a while only for those who have been informed.
2010-02-25 06:02:39 -05:00
.if ${MACHINE_ARCH} == "alpha" || ${MACHINE_ARCH} == "amd64" || ${MACHINE_ARCH} == "sparc64" || ${MACHINE_ARCH:Mmips64*}
Set PKG_ARGS while setting NO64BIT
2006-10-02 16:29:40 -04:00
PKG_ARGS+= -Dmm=0
Python 2.1.2 and Python 2.2. Major changes: - no more threads flavor, threads is now the default. - subpackage modules that depend on other packages instead of having largely redundant flavors (unless platform has no shared libs, then flavors count again) - shared libpython stuff disabled until someone can figure out why it makes Zope crash
2002-02-15 14:42:18 -05:00
.else
Set PKG_ARGS while setting NO64BIT
2006-10-02 16:29:40 -04:00
PKG_ARGS+= -Dmm=1
Python 2.1.2 and Python 2.2. Major changes: - no more threads flavor, threads is now the default. - subpackage modules that depend on other packages instead of having largely redundant flavors (unless platform has no shared libs, then flavors count again) - shared libpython stuff disabled until someone can figure out why it makes Zope crash
2002-02-15 14:42:18 -05:00
.endif
Unbreak packaging of python2.6 on powerpc; ctypes module will need more work. ok djm@
2009-09-22 17:31:00 -04:00
# XXX fix ctypes on powerpc for python2.6
fix compilation on ARM, where the ctypes module is not supported by moving it into a new PFRAG; feedback and ok alek@
2006-11-08 14:00:19 -05:00
# The ctypes module is not supported on all platforms (in particular, ARM)
Prepare for Python-2.6 Flip default ALL_TARGET to the one that will be used for current and future (>=2.5) Python releases, move old default down into 2.3 and 2.4 Makefiles Turn on a verbose retry when regress tests fail; saves messing with LD_LIBRARY_PATH incantations to get them to rerun Take maintainership
2008-10-18 07:55:57 -04:00
.if ${VERSION} == "2.5" || ${VERSION} == "2.6"
fix compilation on ARM, where the ctypes module is not supported by moving it into a new PFRAG; feedback and ok alek@
2006-11-08 14:00:19 -05:00
. if ${MACHINE_ARCH} == "i386" || ${MACHINE_ARCH} == "amd64" || \
${MACHINE_ARCH} == "sparc" || ${MACHINE_ARCH} == "sparc64" || \
${MACHINE_ARCH} == "alpha" || ${MACHINE_ARCH} == "m68k" || \
- extend archtecture tests for mips64el ok naddy@ phessler@
2010-02-09 07:23:59 -05:00
${MACHINE_ARCH:Mmips64*} || \
Unbreak packaging of python2.6 on powerpc; ctypes module will need more work. ok djm@
2009-09-22 17:31:00 -04:00
( ${MACHINE_ARCH} == "powerpc" && ${VERSION} != "2.6" )
fix compilation on ARM, where the ctypes module is not supported by moving it into a new PFRAG; feedback and ok alek@
2006-11-08 14:00:19 -05:00
PKG_ARGS+= -Dctypes=1
. else
PKG_ARGS+= -Dctypes=0
. endif
.endif
Updates and garbage collect all three Python ports: 2.4.4 => 2.4.8 2.5.2 => 2.5.4 2.6 => 2.6.1 Python 2.4 and 2.5 lose their build knobs to match 2.6. Removes no longer needed Python 2.5 security patches backported from the release25-maint SVN branch. Remove the -bz2 subpackage from all three versions. It is silly to make a subpackage to avoid depending on something tiny and compatibly licensed. Python 2.4 and 2.5 lose their -expat subpackages; expat has been in base for some time. Python 2.5 loses its sqlite subpackge. Again, sqlite is tiny, compatibly licensed and is depended upon by more and more applications. This brings it into line with the 2.6 version. Rework all three version's handling of setup.py. Rather than regex replacing LOCALBASE and X11BASE into setup.py post-configure, these are passed in though environment variables. Will save hours of frustrated cursing familiar to anyone who has accidently used the update-patches target after configure and had to go back and redo all the substitutions. Rework the patching of setup.py for 2.4 and 2.5 to be more like what we do for 2.6. I.e. keep the diff minimal and avoid deleting huge blocks of code, so the diff has a chance of applying without massive hand-editing each patch release. Fix .py paths in installed .pyc files (patch from eric@) feedback from several, particularly eric@, ajacoutot@ and Ingo Schwarze; "get it in" ajacoutot@
2009-01-01 16:03:27 -05:00
USE_X11= Yes
AUTOCONF_VERSION?= 2.59
CONFIGURE_STYLE= autoconf
CONFIGURE_ARGS+= ${CONFIGURE_SHARED}
# --srcdir is needed for systrace to work correctly
CONFIGURE_ARGS+= --with-fpectl --with-threads --srcdir=${WRKSRC}
CONFIGURE_ARGS+= --enable-ipv6
# THREAD_STACK_SIZE value might be changed by particular python release
THREAD_STACK_SIZE?=0x20000
increase THREAD_STACK_SIZE for use with www/zope; >From: MAINTAINER.
2004-08-08 11:38:00 -04:00
CONFIGURE_ENV+= OPT='${CFLAGS} -DTHREAD_STACK_SIZE=${THREAD_STACK_SIZE} -fPIC' \
Updates and garbage collect all three Python ports: 2.4.4 => 2.4.8 2.5.2 => 2.5.4 2.6 => 2.6.1 Python 2.4 and 2.5 lose their build knobs to match 2.6. Removes no longer needed Python 2.5 security patches backported from the release25-maint SVN branch. Remove the -bz2 subpackage from all three versions. It is silly to make a subpackage to avoid depending on something tiny and compatibly licensed. Python 2.4 and 2.5 lose their -expat subpackages; expat has been in base for some time. Python 2.5 loses its sqlite subpackge. Again, sqlite is tiny, compatibly licensed and is depended upon by more and more applications. This brings it into line with the 2.6 version. Rework all three version's handling of setup.py. Rather than regex replacing LOCALBASE and X11BASE into setup.py post-configure, these are passed in though environment variables. Will save hours of frustrated cursing familiar to anyone who has accidently used the update-patches target after configure and had to go back and redo all the substitutions. Rework the patching of setup.py for 2.4 and 2.5 to be more like what we do for 2.6. I.e. keep the diff minimal and avoid deleting huge blocks of code, so the diff has a chance of applying without massive hand-editing each patch release. Fix .py paths in installed .pyc files (patch from eric@) feedback from several, particularly eric@, ajacoutot@ and Ingo Schwarze; "get it in" ajacoutot@
2009-01-01 16:03:27 -05:00
LDFLAGS='-L${WRKSRC}' SVNVERSION=no \
LOCALBASE=${LOCALBASE} X11BASE=${X11BASE}
MAKE_ENV+= LOCALBASE=${LOCALBASE} X11BASE=${X11BASE}
MAKE_FLAGS+= LDLIBRARY=libpython${VERSION}.so.${LIBpython${VERSION}_VERSION}
MAKE_FLAGS+= LD_LIBRARY_PATH=${WRKSRC} PATH="${WRKDIST}:${PORTPATH}"
tweak FAKE_FLAGS semantics to saner defaults.
2008-01-04 12:48:33 -05:00
FAKE_FLAGS+= RANLIB=:
Python 2.1.2 and Python 2.2. Major changes: - no more threads flavor, threads is now the default. - subpackage modules that depend on other packages instead of having largely redundant flavors (unless platform has no shared libs, then flavors count again) - shared libpython stuff disabled until someone can figure out why it makes Zope crash
2002-02-15 14:42:18 -05:00
Prepare for Python-2.6 Flip default ALL_TARGET to the one that will be used for current and future (>=2.5) Python releases, move old default down into 2.3 and 2.4 Makefiles Turn on a verbose retry when regress tests fail; saves messing with LD_LIBRARY_PATH incantations to get them to rerun Take maintainership
2008-10-18 07:55:57 -04:00
ALL_TARGET?= everything ./Lib/plat-openbsd4
Python 2.1.2 and Python 2.2. Major changes: - no more threads flavor, threads is now the default. - subpackage modules that depend on other packages instead of having largely redundant flavors (unless platform has no shared libs, then flavors count again) - shared libpython stuff disabled until someone can figure out why it makes Zope crash
2002-02-15 14:42:18 -05:00
post-configure:
@cd ${WRKSRC} && ${MAKE_PROGRAM} Makefile
post-install:
more cleanups in preparation for 2.2 update and 2.3 import from Aleksander Piotrowski <aleksander dot piotrowski at nic dot com dot pl> - fix MASTER_SITES - --without-pymalloc is not needed in 2.1 and 2.2 as it is disabled by default this will allow using it in 2.3 - some PREFIX -> LOCALBASE cleanup - patch distributed pydoc instead of providing our own 3-liner - some improvements on sparc64 - teach regression suite about openbsd - regen some patch files
2003-12-30 12:05:30 -05:00
${INSTALL_SCRIPT} ${WRKSRC}/Tools/scripts/pydoc \
${PREFIX}/bin/pydoc${VERSION}
new packages -gdbm (GNU DBM support) and -idle (split from -tools) from new maintainer Aleksander Piotrowski <aleksander dot piotrowski at nic dot com dot pl> more to come
2003-12-13 10:03:07 -05:00
@sed -e "s,@VERSION@,${VERSION},g" -e "s,@LOCALBASE@,${LOCALBASE},g" \
${FILESDIR}/idle > ${WRKSRC}/idle
${INSTALL_SCRIPT} ${WRKSRC}/idle ${PREFIX}/bin/idle${VERSION}
Python 2.1.2 and Python 2.2. Major changes: - no more threads flavor, threads is now the default. - subpackage modules that depend on other packages instead of having largely redundant flavors (unless platform has no shared libs, then flavors count again) - shared libpython stuff disabled until someone can figure out why it makes Zope crash
2002-02-15 14:42:18 -05:00
@cd ${WRKSRC}; tar -cf - Tools | (cd ${PREFIX}/lib/python${VERSION}; \
tar -xf -)
- 2.2 -> 2.2.1 - annotate patches submitted to Python patch tracker - 100% license compliance: install CHANGES.OpenBSD file
2002-05-11 17:35:13 -04:00
${INSTALL_DATA_DIR} ${PREFIX}/share/doc/python${VERSION}
${INSTALL_DATA} ${FILESDIR}/CHANGES.OpenBSD \
${PREFIX}/share/doc/python${VERSION}/CHANGES.OpenBSD
Prepare for Python-2.6 Flip default ALL_TARGET to the one that will be used for current and future (>=2.5) Python releases, move old default down into 2.3 and 2.4 Makefiles Turn on a verbose retry when regress tests fail; saves messing with LD_LIBRARY_PATH incantations to get them to rerun Take maintainership
2008-10-18 07:55:57 -04:00
.if ${VERSION} == "2.5" || ${VERSION} == "2.6"
Let 2.5 install python-mode for emacs. ok mbalmer@
2008-05-10 13:10:24 -04:00
${INSTALL_DATA_DIR} ${PREFIX}/share/emacs/site-lisp
${INSTALL_DATA} ${WRKSRC}/Misc/python-mode.el \
avoid conflict in -tools subpackage
2009-06-24 21:49:54 -04:00
${PREFIX}/share/emacs/site-lisp/python-mode-${VERSION}.el
Let 2.5 install python-mode for emacs. ok mbalmer@
2008-05-10 13:10:24 -04:00
.endif
Updates and garbage collect all three Python ports: 2.4.4 => 2.4.8 2.5.2 => 2.5.4 2.6 => 2.6.1 Python 2.4 and 2.5 lose their build knobs to match 2.6. Removes no longer needed Python 2.5 security patches backported from the release25-maint SVN branch. Remove the -bz2 subpackage from all three versions. It is silly to make a subpackage to avoid depending on something tiny and compatibly licensed. Python 2.4 and 2.5 lose their -expat subpackages; expat has been in base for some time. Python 2.5 loses its sqlite subpackge. Again, sqlite is tiny, compatibly licensed and is depended upon by more and more applications. This brings it into line with the 2.6 version. Rework all three version's handling of setup.py. Rather than regex replacing LOCALBASE and X11BASE into setup.py post-configure, these are passed in though environment variables. Will save hours of frustrated cursing familiar to anyone who has accidently used the update-patches target after configure and had to go back and redo all the substitutions. Rework the patching of setup.py for 2.4 and 2.5 to be more like what we do for 2.6. I.e. keep the diff minimal and avoid deleting huge blocks of code, so the diff has a chance of applying without massive hand-editing each patch release. Fix .py paths in installed .pyc files (patch from eric@) feedback from several, particularly eric@, ajacoutot@ and Ingo Schwarze; "get it in" ajacoutot@
2009-01-01 16:03:27 -05:00
REGRESS_TARGET= test
REGRESS_FLAGS= "EXTRATESTOPTS=-w"
# Some regress tests write to $HOME
PORTHOME= ${WRKDIR}
Reference in New Issue Copy Permalink