Date: Tue, 21 Dec 2010 01:29:37 -0500 From: Chris Brennan <xaero@xaerolimit.net> To: FreeBSD Questions <freebsd-questions@freebsd.org> Subject: devel/py-dbus Message-ID: <AANLkTimyAXd7GH0mGNTZzqr7nhrL69P7MQ1P_7b8c5b6@mail.gmail.com>
next in thread | raw e-mail | index | archive | help
I've been trying to do a portupgrade -a for the last month and I have been
running into snags of all sorts. This one is with python
The system is FreeBSD7.3/i386 (PIII/800Mhz, 384MB of ram)
FreeBSD ziggy.xaerolimit.net 7.3-RELEASE-p3 FreeBSD 7.3-RELEASE-p3 #8: Sun
Oct 24 01:53:03 EDT 2010 root@ziggy.xaerolimit.net:/usr/obj/usr/src/sys/ZIGGY
i386
===>>> Updating dependency entry for dbus-glib-0.88 in each dependent port
===>>> Re-installation of dbus-glib-0.88 succeeded
===>>> Delete dbus-1.4.0.tar.gz? y/n [n]
===>>> Returning to dependency check for devel/py-dbus
===>>> Dependency check complete for devel/py-dbus
===> Cleaning for py26-dbus-0.83.1_1
===> License check disabled, port has not defined LICENSE
===> Extracting for py26-dbus-0.83.1_1
=> SHA256 Checksum OK for dbus-python-0.83.1.tar.gz.
===> Patching for py26-dbus-0.83.1_1
===> py26-dbus-0.83.1_1 depends on file: /usr/local/bin/python2.6 - found
===> py26-dbus-0.83.1_1 depends on executable: gmake - found
===> py26-dbus-0.83.1_1 depends on package: libtool>=2.2 - found
===> py26-dbus-0.83.1_1 depends on shared library: dbus-glib-1.2 - found
===> py26-dbus-0.83.1_1 depends on shared library: intl - found
===> Configuring for py26-dbus-0.83.1_1
checking for a BSD-compatible install... /usr/bin/install -c -o root -g
wheel
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... ./install-sh -c -d
checking for gawk... no
checking for mawk... no
checking for nawk... nawk
checking whether gmake sets $(MAKE)... yes
checking build system type... i386-portbld-freebsd7.3
checking host system type... i386-portbld-freebsd7.3
checking for style of include used by gmake... GNU
checking for gcc... cc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether cc accepts -g... yes
checking for cc option to accept ISO C89... none needed
checking dependency style of cc... gcc3
checking for a sed that does not truncate output... /usr/local/bin/gsed
checking for grep that handles long lines and -e... /usr/bin/grep
checking for egrep... /usr/bin/grep -E
checking for fgrep... /usr/bin/grep -F
checking for ld used by cc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... (cached) 262144
checking whether the shell understands some XSI constructs... yes
checking whether the shell understands "+="... no
checking for /usr/bin/ld option to reload object files... -r
checking for objdump... objdump
checking how to recognize dependent libraries... pass_all
checking for ar... ar
checking for strip... strip
checking for ranlib... ranlib
checking command to parse /usr/bin/nm -B output from cc object... ok
checking how to run the C preprocessor... cpp
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for dlfcn.h... yes
checking for objdir... .libs
checking if cc supports -fno-rtti -fno-exceptions... no
checking for cc option to produce PIC... -fPIC -DPIC
checking if cc PIC flag -fPIC -DPIC works... yes
checking if cc static flag -static works... yes
checking if cc supports -c -o file.o... yes
checking if cc supports -c -o file.o... (cached) yes
checking whether the cc linker (/usr/bin/ld) supports shared libraries...
yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... freebsd7.3 ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... no
checking whether /usr/local/bin/python2.6 version >= 2.4.0... yes
checking for /usr/local/bin/python2.6 version... 2.6
checking for /usr/local/bin/python2.6 platform... freebsd7
checking for /usr/local/bin/python2.6 script directory...
${prefix}/lib/python2.6/
site-packages
checking for /usr/local/bin/python2.6 extension module directory...
${exec_prefix}
/lib/python2.6/site-packages
checking for Python headers using /usr/local/bin/python2.6-config
--includes... -I
/usr/local/include/python2.6 -I/usr/local/include/python2.6
checking whether those headers are sufficient... no
configure: error: could not find Python headers
===> Script "configure" failed unexpectedly.
Please run the gnomelogalyzer, available from
"http://www.freebsd.org/gnome/gnomelogalyzer.sh", which will diagnose the
problem and suggest a solution. If - and only if - the gnomelogalyzer cannot
solve the problem, report the build failure to the FreeBSD GNOME team at
gnome@FreeBSD.org, and attach (a)
"/usr/ports/devel/py-dbus/work/dbus-python-0.83.1/config.log", (b) the
output
of the failed make command, and (c) the gnomelogalyzer output. Also, it
might
be a good idea to provide an overview of all packages installed on your
system
(i.e. an `ls /var/db/pkg`). Put your attachment up on any website,
copy-and-paste into http://freebsd-gnome.pastebin.com, or use send-pr(1)
with
the attachment. Try to avoid sending any attachments to the mailing list
(gnome@FreeBSD.org), because attachments sent to FreeBSD mailing lists are
usually discarded by the mailing list software.
*** Error code 1
Stop in /usr/ports/devel/py-dbus.
===>>> make failed for devel/py-dbus
===>>> Aborting update
===>>> There are messages from installed ports to display,
but first take a moment to review the error messages
above. Then press Enter when ready to proceed.
The above error was received by passing 'cd /usr/ports/lang/python && make
upgrade-site-packages -DUSE_PORTMASTER' python2.6 is the only version of
python installed and the above cmd was gotten from /usr/ports/UPDATING ...
did I miss something or is this system just flushed itself?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTimyAXd7GH0mGNTZzqr7nhrL69P7MQ1P_7b8c5b6>