2

===>  Configuring for gobject-introspection-0.6.14
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... /usr/local/bin/gmkdir -p
checking for gawk... no
checking for mawk... no
checking for nawk... nawk
checking whether gmake sets $(MAKE)... yes
checking whether to enable maintainer-specific portions of Makefiles... no
checking build system type... i386-portbld-freebsd8.0
checking host system type... i386-portbld-freebsd8.0
checking for Win32... no
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 for style of include used by gmake... GNU
checking dependency style of cc... gcc3
checking whether cc understands -c and -o together... yes
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... cc -E
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... freebsd8.0 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... yes
checking for pkg-config... /usr/local/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for flex... flex
checking lex output file root... lex.yy
checking lex library... -lfl
checking whether yytext is a pointer... yes
checking for bison... bison -y
GI_ENABLE_GCOV: not found
checking for dlopen in -ldl... no
checking for the suffix of shared libraries... .so
checking for GOBJECT... configure: error: Package requirements (gobject-2.0 gio-2.0) were not met:

gnome-config: not found
No package 'gobject-2.0' found
gnome-config: not found
No package 'gio-2.0' found

Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.

Alternatively, you may set the environment variables GOBJECT_CFLAGS
and GOBJECT_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.

===>  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/gobject-introspection/work/gobject-introspection-0.6.14/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/gobject-introspection.
*** Error code 1

Stop in /usr/ports/sysutils/polkit.
*** Error code 1

Stop in /usr/ports/sysutils/polkit-qt.
[root@mainserver.serveftp.org /usr/ports/sysutils/polkit-qt]# fetch http://www.freebsd.org/gnome/gnomelogalyzer.sh
gnomelogalyzer.sh                             100% of 7870  B   19 kBps
[root@mainserver.serveftp.org /usr/ports/sysutils/polkit-qt]# chmod +x gnomelogalyzer.sh
[root@mainserver.serveftp.org /usr/ports/sysutils/polkit-qt]# ./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 freebsd-gnome@FreeBSD.org,
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 your cvsup(1) configuration file specifies the 'ports-all'
          collection
        * Run cvsup(1) and attempt the build again
        * 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 freebsd-gnome@FreeBSD.org.  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.