xxavi@casa:/home/xxavi % su
Password:
You have mail.
root@casa:/home/xxavi # cd /usr/ports/graphics/py-cairo/
root@casa:/usr/ports/graphics/py-cairo # pwd
/usr/ports/graphics/py-cairo
root@casa:/usr/ports/graphics/py-cairo # make clean rmconfig
===>  Cleaning for py27-cairo-1.8.10_1
===> No user-specified options configured for py27-cairo-1.8.10_1
root@casa:/usr/ports/graphics/py-cairo # ls -l
total 24
-rw-r--r--  1 root  wheel  1000 Nov 17 06:58 Makefile
-rw-r--r--  1 root  wheel   138 Nov 20  2010 distinfo
-rwxr-xr-x  1 root  wheel  7805 Jan  6 15:47 gnomelogalyzer.sh
-rw-r--r--  1 root  wheel    89 Mar 11  2005 pkg-descr
-rw-r--r--  1 root  wheel   311 Oct 14  2006 pkg-plist
root@casa:/usr/ports/graphics/py-cairo # md5 *
MD5 (Makefile) = c917545d4182276b251a3a7f8d74fe1a
MD5 (distinfo) = 53adce0d5051066565025b727f38d379
MD5 (gnomelogalyzer.sh) = de95158bb45e5ac4a5674c5755efad81
MD5 (pkg-descr) = 27d5cc0e01fbdcda9959608745a878ea
MD5 (pkg-plist) = b8bf66847d07f050af165948d7f798e9
root@casa:/usr/ports/graphics/py-cairo # make depends
===>   py27-cairo-1.8.10_1 depends on shared library: cairo.2 - found
===>   py27-cairo-1.8.10_1 depends on file: /usr/local/bin/python2.7 - found
===>   py27-cairo-1.8.10_1 depends on executable: gmake - found
===>   py27-cairo-1.8.10_1 depends on file: /usr/local/bin/python2.7 - found
root@casa:/usr/ports/graphics/py-cairo # make
===>  Found saved configuration for cairo-1.10.2_5,2
===>  Extracting for py27-cairo-1.8.10_1
=> SHA256 Checksum OK for py2cairo-1.8.10.tar.gz.
===>  Patching for py27-cairo-1.8.10_1
===>   py27-cairo-1.8.10_1 depends on file: /usr/local/bin/python2.7 - found
===>   py27-cairo-1.8.10_1 depends on executable: gmake - found
===>   py27-cairo-1.8.10_1 depends on shared library: cairo.2 - found
===>  Configuring for py27-cairo-1.8.10_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... gawk
checking whether gmake sets $(MAKE)... yes
checking build system type... i386-portbld-freebsd9.1
checking host system type... i386-portbld-freebsd9.1
checking for style of include used by gmake... GNU
checking for gcc... cc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
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/bin/sed
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 sys/stat.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... freebsd9.1 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
configure: creating ./config.lt
config.lt: creating libtool
checking whether /usr/local/bin/python2.7 version >= 2.6... yes
checking for /usr/local/bin/python2.7 version... 2.7
checking for /usr/local/bin/python2.7 platform... freebsd9
checking for /usr/local/bin/python2.7 script directory... ${prefix}/lib/python2.7/site-packages
checking for /usr/local/bin/python2.7 extension module directory... ${exec_prefix}/lib/python2.7/site-packages
checking for pkg-config... /usr/local/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for CAIRO... yes
checking for XPYB... no
checking for headers required to compile python extensions... not found
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
[email protected], and attach (a)
"/usr/ports/graphics/py-cairo/work/pycairo-1.8.10/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
([email protected]), because attachments sent to FreeBSD mailing lists are
usually discarded by the mailing list software.
*** [do-configure] Error code 1

Stop in /usr/ports/graphics/py-cairo.
root@casa:/usr/ports/graphics/py-cairo # wget http://www.freebsd.org/gnome/gnomelogalyzer.sh
--2013-01-10 11:29:22--  http://www.freebsd.org/gnome/gnomelogalyzer.sh
Resolving www.freebsd.org (www.freebsd.org)... 8.8.178.110, 2001:1900:2254:206a::50:0
Connecting to www.freebsd.org (www.freebsd.org)|8.8.178.110|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [application/octet-stream]
Saving to: `gnomelogalyzer.sh.1'

    [ <=>                                                   ] 7,805       40.2K/s   in 0.2s

2013-01-10 11:29:22 (40.2 KB/s) - `gnomelogalyzer.sh.1' saved [7805]

root@casa:/usr/ports/graphics/py-cairo # chmod +x gnomelogalyzer.sh
root@casa:/usr/ports/graphics/py-cairo # ./gnomelogalyzer.sh

Generating build log. Please wait... done.

The cause of your build failure is not known to gnomelogalyzer.sh.  Before
e-mailing the build log to the FreeBSD GNOME team at [email protected],
TRY EACH OF THE FOLLOWING:

  * If you are generating your own logfile, make sure to generate it with
    something similar to:
	  "make 2>&1 | tee /path/to/logfile" (sh/bash/ksh/zsh) or
	  "make |& tee /path/to/logfile" (csh/tcsh)
	* Make sure you are downloading the complete Ports tree.
	* Check /usr/ports/UPDATING for information pertinent to your build
	  failure
	* 99% of the commonly reported build failures can be solved by
	  running "portupgrade -a"
	* Read the FAQs at http://www.FreeBSD.org/gnome/
	* Search the archives of [email protected].  Archives can be
	  searched at http://www.freebsd.org/gnome/index.html#search

If you have not performed each of the above suggestions, don't bother asking
for help.  The chances are good that you'll simply be told to perform one of
the aforementioned steps.
root@casa:/usr/ports/graphics/py-cairo # md5 gnomelogalyzer.sh
MD5 (gnomelogalyzer.sh) = de95158bb45e5ac4a5674c5755efad81
root@casa:/usr/ports/graphics/py-cairo # make |& tee ./graphics_py-cairo_logfile.txt
===>   py27-cairo-1.8.10_1 depends on file: /usr/local/bin/python2.7 - found
===>   py27-cairo-1.8.10_1 depends on executable: gmake - found
===>   py27-cairo-1.8.10_1 depends on shared library: cairo.2 - found
===>  Configuring for py27-cairo-1.8.10_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... gawk
checking whether gmake sets $(MAKE)... yes
checking build system type... i386-portbld-freebsd9.1
checking host system type... i386-portbld-freebsd9.1
checking for style of include used by gmake... GNU
checking for gcc... cc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
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/bin/sed
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 sys/stat.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... freebsd9.1 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
configure: creating ./config.lt
config.lt: creating libtool
checking whether /usr/local/bin/python2.7 version >= 2.6... yes
checking for /usr/local/bin/python2.7 version... 2.7
checking for /usr/local/bin/python2.7 platform... freebsd9
checking for /usr/local/bin/python2.7 script directory... ${prefix}/lib/python2.7/site-packages
checking for /usr/local/bin/python2.7 extension module directory... ${exec_prefix}/lib/python2.7/site-packages
checking for pkg-config... /usr/local/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for CAIRO... yes
checking for XPYB... no
checking for headers required to compile python extensions... not found
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
[email protected], and attach (a)
"/usr/ports/graphics/py-cairo/work/pycairo-1.8.10/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
([email protected]), because attachments sent to FreeBSD mailing lists are
usually discarded by the mailing list software.
*** [do-configure] Error code 1

Stop in /usr/ports/graphics/py-cairo.
root@casa:/usr/ports/graphics/py-cairo # ls -l graphics_py-cairo_logfile.txt
-rw-r--r--  1 root  wheel  4971 Jan 10 11:30 graphics_py-cairo_logfile.txt
root@casa:/usr/ports/graphics/py-cairo # md5 graphics_py-cairo_logfile.txt
MD5 (graphics_py-cairo_logfile.txt) = 73c264f0655b7598755832ae76b4cbfa
root@casa:/usr/ports/graphics/py-cairo #