=> Bootstrap dependency digest>=20010302: found digest-20121220 => Checksum SHA1 OK for subversion-1.7.9.tar.bz2 => Checksum RMD160 OK for subversion-1.7.9.tar.bz2 ===> Installing dependencies for py26-subversion-1.7.9 ========================================================================== The supported build options for py26-subversion are: apr1 sasl serf The currently selected options are: apr1 You can select which build options to use by setting PKG_DEFAULT_OPTIONS or the following variable. Its current value is shown: PKG_OPTIONS.subversion (not defined) ========================================================================== ========================================================================== The following variables will affect the build process of this package, py26-subversion-1.7.9. Their current value is shown below: * PYTHON_VERSION_DEFAULT = 27 * SSLBASE = /usr * SSLCERTS = /etc/openssl/certs * SSLDIR = /etc/openssl * SSLKEYS = /etc/openssl/private Based on these variables, the following variables have been set: * PYPACKAGE = python26 You may want to abort the process now with CTRL-C and change their value before continuing. Be sure to run `/usr/bin/make clean' after the changes. ========================================================================== => Tool dependency libtool-base>=2.2.6bnb3: found libtool-base-2.4.2nb3 => Tool dependency checkperms>=1.1: found checkperms-1.11 => Full dependency neon>=0.29.6nb3: found neon-0.29.6nb4 => Full dependency subversion-base>=1.7.9: found subversion-base-1.7.9 => Full dependency python26>=2.6.6nb8: found python26-2.6.8nb3 ===> Overriding tools for py27-subversion-1.7.9 ===> Extracting for py27-subversion-1.7.9 ===> Patching for py27-subversion-1.7.9 => Applying pkgsrc patches for py27-subversion-1.7.9 => Verifying /usr/pkgsrc/devel/py-subversion/../../devel/subversion/patches/patch-ad => Applying pkgsrc patch /usr/pkgsrc/devel/py-subversion/../../devel/subversion/patches/patch-ad Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-ad,v 1.15 2011/03/04 03:12:36 taca Exp $ | |--- Makefile.in.orig 2010-11-25 17:55:59.000000000 +0000 |+++ Makefile.in -------------------------- Patching file Makefile.in using Plan A... Hunk #1 succeeded at 736 (offset 54 lines). done => Verifying /usr/pkgsrc/devel/py-subversion/../../devel/subversion/patches/patch-ae => Applying pkgsrc patch /usr/pkgsrc/devel/py-subversion/../../devel/subversion/patches/patch-ae Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-ae,v 1.19 2013/02/09 13:22:10 ryoon Exp $ | |Second hunk is subversion Revision 1145203. Ensure the |Perl extension is built using the Perl compiler flags. | |--- subversion/bindings/swig/perl/native/Makefile.PL.in.orig 2012-09-30 04:02:09.000000000 +0000 |+++ subversion/bindings/swig/perl/native/Makefile.PL.in -------------------------- Patching file subversion/bindings/swig/perl/native/Makefile.PL.in using Plan A... Hunk #1 succeeded at 35. done /bin/rm /scratch/devel/py-subversion/work/subversion-1.7.9/build-outputs.mk /bin/cp /usr/pkgsrc/devel/py-subversion/../../devel/subversion/files/build-outputs.mk /scratch/devel/py-subversion/work/subversion-1.7.9/build-outputs.mk ===> Creating toolchain wrappers for py27-subversion-1.7.9 /bin/mkdir -p /scratch/devel/py-subversion/work/.buildlink/bin && /bin/ln -fs apr-1-config /scratch/devel/py-subversion/work/.buildlink/bin/apr-config /bin/mkdir -p /scratch/devel/py-subversion/work/.buildlink/bin && /bin/ln -fs apu-1-config /scratch/devel/py-subversion/work/.buildlink/bin/apu-config ERROR: python27>=2.7 python27>=2.7 is not installed; can't buildlink files. *** Error code 1 Stop. make: stopped in /usr/pkgsrc/devel/py-subversion *** Error code 1 Stop. make: stopped in /usr/pkgsrc/devel/py-subversion