Date: Mon, 08 Dec 2014 09:38:28 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 195803] New: dns/unbound Message-ID: <bug-195803-13@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195803 Bug ID: 195803 Summary: dns/unbound Product: Ports Tree Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: sem@FreeBSD.org Reporter: freebsd@dckd.nl Assignee: sem@FreeBSD.org Flags: maintainer-feedback?(sem@FreeBSD.org) Created attachment 150341 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=150341&action=edit config.log When upgrading my unbound port, I have run into a problem with its python support. As far as I know I do not have any special python configuration. unbound/ $ sudo make ===> License BSD4CLAUSE accepted by the user ===> Found saved configuration for unbound-1.4.22_4 ===> unbound-1.5.0 depends on file: /usr/local/sbin/pkg - found ===> Fetching all distfiles required by unbound-1.5.0 for building ===> Extracting for unbound-1.5.0 => SHA256 Checksum OK for unbound-1.5.0.tar.gz. ===> Patching for unbound-1.5.0 ===> unbound-1.5.0 depends on executable: swig - found ===> unbound-1.5.0 depends on file: /usr/local/lib/libcrypto.so.8 - found ===> unbound-1.5.0 depends on executable: gmake - found ===> unbound-1.5.0 depends on file: /usr/local/bin/python2.7 - found ===> unbound-1.5.0 depends on shared library: libexpat.so - found (/usr/local/lib/libexpat.so.6.0.0) ===> unbound-1.5.0 depends on shared library: libldns.so - found (/usr/local/lib/libldns.so.1.6.17) [....] checking for python... /usr/local/bin/python2.7 checking for the distutils Python package... yes checking for Python include path... -I/usr/local/include/python2.7 checking for Python library path... -L. -lpython2.7 checking for Python site-packages path... /usr/local/lib/python2.7/site-packages checking consistency of all components of python development environment... no configure: error: Could not link test program to Python. Maybe the main Python library has been installed in some non-standard library path. If so, pass it to configure, via the LDFLAGS environment variable. Example: ./configure LDFLAGS="-L/usr/non-standard-path/python/lib" ============================================================================ ERROR! You probably have to install the development version of the Python package for your distribution. The exact name of this package varies among them. ============================================================================ ===> Script "configure" failed unexpectedly. --- Comment #1 from Bugzilla Automation <bugzilla@FreeBSD.org> --- Auto-assigned to maintainer sem@FreeBSD.org -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-195803-13>