ports/lang/python27, branch 2014Q3

Support LIBS like LDFLAGS.

2014-06-11T14:49:59Z

- Add LIBS="${LIBS}" to MAKE_ENV and CONFIGURE_ENV. - Add an option helper for LIBS. - Adjust all ports that already use LIBS. Also remove references to PTHREAD_CFLAGS and PTHREAD_LIBS while here. - Some ports did not support having a LIBS environment variable and required additional patches. Somewhat simplified a linker command line looks like: ${CC} ${src_LDFLAGS} ${LDFLAGS} ${src_LIBS} ${LIBS} where src_LDFLAGS and src_LIBS are controlled by upstream and LDFLAGS and LIBS can be controlled by us. If possible -L and -l flags need to be added to LIBS to make sure they appear after any -L and -l flags set by upstream. Many ports currently add -L${LOCALBASE}/lib to LDFLAGS but this may appear too early on the command line causing installed libraries to be linked in instead of freshly built ones. Additional changes: benchmarks/netio: Replace WITH_IPV6 with an IPV6 option. comms/gnokii: Replace some patches with USES=pathfix. Also remove -fPIC. graphics/gimageview: USES=libtool and install desktop file in DESKTOPDIR. graphics/visionworkbench: Remove FreeBSD 7 support. multimedia/libmovtar: New LIB_DEPENDS syntax. multimedia/opencinematools: Use standard do-build. net/siproxd: USES=libtool:keepla (port actually needs .la files for plugins) net-mgmt/nagios: Remove -fPIC. net-mgmt/nagios4: Remove -fPIC. print/cups-base: Only add -lssp_nonshared on i386 and OSVERSION < 1000036. security/p11-kit: Replace PTHREAD_LIBS in CONFIGURE_ENV with ac_cv_func_pthread_mutexattr_init=no in CONFIGURE_ARGS. This skips a test in configure that falsely detects pthread_mutexattr_init in our libc. sysutils/dar: Fix iconv detection. x11/rxvt-unicode: Remove -lstdc++ and patch configure to remove a FreeBSD hack and use $CXX as linker as on other platforms. PR: 190592 Exp-run by: antoine Approved by: portmgr (antoine)

lang/python{27,31,32}: Replace USE_XZ with USES=tar:xz

2014-04-22T14:37:04Z

USE_XZ has been deprecated, replace it with the new USES value. Python 3.3 and 3.4 ports have already been converted.

lang/python{31,32,33}: Fix stage/package as non-root

2014-04-22T12:14:26Z

Copy the second part of a change previously made to python27 [1], to python31, python32 and python33. This fixes staging and packaging of these ports by a non-root user by running ranlib on the archive prior to it being installed read-only. While I'm here: - python27: Add breadcrumbs and references to the patch header - python34: Update breadcrumbs and references to the patch header [1] https://svnweb.freebsd.org/ports?view=revision&revision=350207 Submitted by: antoine Reviewed by: kwm, sbz

lang/python{31,32,33}: Add clang 3.4 fix from python27

2014-04-20T01:35:39Z

Copy change committed to python27 [1] to python31, python32 and python33 to fix builds of some extensions with Clang 3.4. Also add breadcrumbs to the patch header in lang/python27 referencing the upstream issue. [2] The Python 3.4 port (lang/python34) already carries the patch. [1] https://svnweb.freebsd.org/ports?view=revision&revision=346428 [2] http://bugs.python.org/issue20767

- Pet portlint: use PYTHON_DISTNAME instead of PYTHON_DISTFILE

2014-04-11T08:25:47Z

Allow staging/packaging as a regular user:

2014-04-05T09:04:28Z

- pycompile only once, previously it would pycompile 3 imported modules (getopt, struct and py_compile) and make them read-only, and later try to pycompile them again and fail - ranlib before installing archive read-only With hat: portmgr

- Fix build with readline 6.3 from ports

2014-03-01T14:10:13Z

the patch was obtained from upstream (issue #20374) - Add missing USES=readline PR: ports/187174 Reported by: O. Hartmann Reviewed by: koobs Obtained from: python

lang/python*: Backport security fix for CVE-2014-1912

2014-03-01T10:52:55Z

A vulnerability was reported [1] in Python's socket module, due to a boundary error within the sock_recvfrom_into() function, which could be exploited to cause a buffer overflow. This could be used to crash a Python application that uses the socket.recvfrom_info() function or, possibly, execute arbitrary code with the permissions of the user running vulnerable Python code. This vulnerable function, socket.recvfrom_into(), was introduced in Python 2.5. Earlier versions are not affected by this flaw. This is fixed in upstream branches for version 2.7, 3.1, 3.2 and 3.3. [1] http://bugs.python.org/issue20246 MFH: 2014Q1 Security: 8e5e6d42-a0fa-11e3-b09a-080027f2d077

Unbreak python module builds across the tree as a result of clang 3.4 import

2014-02-28T03:04:19Z

now disallowing the use of -R. Submitted by: antoine Reviewed by: gjb

- Fix bad libpython* symlinks after enabling the lang/python* ports to

2014-02-01T09:21:23Z

be stagedir-aware PR: ports/186284 Submitted by: marino@ Pointyhat to: myself