gnome-keyring-2.24.1_1

Kevin Oberman oberman at es.net
Fri Jan 16 10:19:12 PST 2009


> Date: Fri, 16 Jan 2009 18:58:14 +0200
> From: Volodymyr Yatsynych <yatsynych at gmail.com>
> Sender: owner-freebsd-gnome at freebsd.org
> 
> # make install clean
> ===>   gnome-keyring-2.24.1_1 depends on executable: gmake - found
> ===>   gnome-keyring-2.24.1_1 depends on file: /usr/local/bin/libtool - 
> found
> ===>   gnome-keyring-2.24.1_1 depends on file: 
> /usr/local/bin/intltool-extract - found
> ===>   gnome-keyring-2.24.1_1 depends on executable: pkg-config - found
> ===>   gnome-keyring-2.24.1_1 depends on shared library: tasn1.3 - found
> ===>   gnome-keyring-2.24.1_1 depends on shared library: gcrypt.16 - found
> ===>   gnome-keyring-2.24.1_1 depends on shared library: hal.1 - found
> ===>   gnome-keyring-2.24.1_1 depends on shared library: intl - found
> ===>   gnome-keyring-2.24.1_1 depends on shared library: atk-1.0.0 - found
> ===>   gnome-keyring-2.24.1_1 depends on shared library: gconf-2.4 - found
> ===>   gnome-keyring-2.24.1_1 depends on shared library: glib-2.0.0 - found
> ===>   gnome-keyring-2.24.1_1 depends on shared library: gtk-x11-2.0.0 - 
> found
> ===>   gnome-keyring-2.24.1_1 depends on shared library: IDL-2.0 - found
> ===>   gnome-keyring-2.24.1_1 depends on shared library: xml2.5 - found
> ===>   gnome-keyring-2.24.1_1 depends on shared library: ORBit-2.0 - found
> ===>   gnome-keyring-2.24.1_1 depends on shared library: pango-1.0.0 - found
> ===>  Configuring for gnome-keyring-2.24.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... /usr/local/bin/gmkdir -p
> checking for gawk... gawk
> checking whether gmake sets $(MAKE)... yes
> checking whether build environment is sane... yes
> checking whether to enable maintainer-specific portions of Makefiles... no
> 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 an ANSI C-conforming const... yes
> checking for library containing strerror... none required
> checking for gcc... (cached) cc
> checking whether we are using the GNU C compiler... (cached) yes
> checking whether cc accepts -g... (cached) yes
> checking for cc option to accept ISO C89... (cached) none needed
> checking dependency style of cc... (cached) gcc3
> checking how to run the C preprocessor... cc -E
> checking whether cc understands -c and -o together... yes
> checking for a BSD-compatible install... /usr/bin/install -c -o root -g 
> wheel
> checking whether ln -s works... yes
> checking whether gmake sets $(MAKE)... (cached) yes
> checking build system type... i386-portbld-freebsd7.1
> checking host system type... i386-portbld-freebsd7.1
> 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 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 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 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... freebsd7.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
> checking whether NLS is requested... yes
> checking for intltool >= 0.35.0... 0.37.1 found
> checking for intltool-update... /usr/local/bin/intltool-update
> checking for intltool-merge... /usr/local/bin/intltool-merge
> checking for intltool-extract... /usr/local/bin/intltool-extract
> checking for xgettext... /usr/local/bin/xgettext
> checking for msgmerge... /usr/local/bin/msgmerge
> checking for msgfmt... /usr/local/bin/msgfmt
> checking for gmsgfmt... /usr/local/bin/msgfmt
> checking for perl... /usr/bin/perl
> checking for XML::Parser... configure: error: XML::Parser perl module is 
> required for intltool
> ===>  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 at FreeBSD.org, and attach (a)
> "/usr/ports/security/gnome-keyring/work/gnome-keyring-2.24.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 at FreeBSD.org), because attachments sent to FreeBSD 
> mailing
> lists are usually discarded by the mailing list software.
> *** Error code 1
> 
> Stop in /usr/ports/security/gnome-keyring.
> *** Error code 1
> 
> Stop in /usr/ports/security/gnome-keyring.
> 

% portupgrade -f p5-XML-Parser

This port needs to be re-installed periodically when things get
updated even though that port itself has not been updated.
-- 
R. Kevin Oberman, Network Engineer
Energy Sciences Network (ESnet)
Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab)
E-mail: oberman at es.net			Phone: +1 510 486-8634
Key fingerprint:059B 2DDF 031C 9BA3 14A4  EADA 927D EBB3 987B 3751


More information about the freebsd-gnome mailing list