==> Synchronizing chroot copy [/home/leming/armv7/root] -> [leming]...done
==> Making package: alleyoop 0.9.8-7 (Wed Mar 27 16:17:54 2019)
==> Retrieving sources...
  -> Found alleyoop-0.9.8.tar.gz
  -> Found alleyoop16.png
  -> Found alleyoop32.png
  -> Found alleyoop64.png
  -> Found alleyoop128.png
  -> Found alleyoop256.png
  -> Found git-fixes.patch
==> Validating source files with sha256sums...
    alleyoop-0.9.8.tar.gz ... Passed
    alleyoop16.png ... Passed
    alleyoop32.png ... Passed
    alleyoop64.png ... Passed
    alleyoop128.png ... Passed
    alleyoop256.png ... Passed
    git-fixes.patch ... Passed
==> Making package: alleyoop 0.9.8-7 (Wed 27 Mar 2019 04:17:56 PM UTC)
==> Checking runtime dependencies...
==> Installing missing dependencies...
resolving dependencies...
looking for conflicting packages...
warning: dependency cycle detected:
warning: harfbuzz will be installed before its freetype2 dependency

Packages (49) atk-2.32-1  avahi-0.7+18+g1b5f401-1  cairo-1.16.0-2  dbus-glib-0.110-1  desktop-file-utils-0.23+4+g92af410-1  fontconfig-2:2.13.1+12+g5f5ec56-1  freetype2-2.10.0-1  fribidi-1.0.5-1  gdk-pixbuf2-2.38.1-1  graphite-1:1.3.13-1  gtk-update-icon-cache-1:3.24.7+25+g17665f06e3-1  harfbuzz-2.3.1-2  hicolor-icon-theme-0.17-1  jasper-2.0.16-1  js52-52.9.0-2  libcups-2.2.11-1  libdaemon-0.14-4  libdatrie-0.2.12-1  libjpeg-turbo-2.0.2-1  libnsl-1.2.0-1  libpng-1.6.36-1  librsvg-2:2.44.13-1  libthai-0.1.28-1  libtiff-4.0.10-1  libx11-1.6.7-1  libxau-1.0.9-1  libxcb-1.13.1-1  libxcomposite-0.4.5-1  libxcursor-1.2.0-1  libxdamage-1.1.5-1  libxdmcp-1.1.3-1  libxext-1.3.4-1  libxfixes-5.0.3-2  libxft-2.3.3-1  libxi-1.7.9-2  libxinerama-1.1.4-1  libxrandr-1.5.2-1  libxrender-0.9.10-2  lzo-2.10-2  pango-1:1.43.0-1  pixman-0.38.0-2  polkit-0.115+24+g5230646-1  python2-2.7.16-1  shared-mime-info-1.12-1  xcb-proto-1.13-2  xorgproto-2018.4-1  gconf-3.2.6+11+g07808097-4  gtk2-2.24.32-1  valgrind-3.14.0-1

Total Download Size:    78.94 MiB
Total Installed Size:  376.26 MiB

:: Proceed with installation? [Y/n] 
:: Retrieving packages...
downloading libnsl-1.2.0-1-armv7h.pkg.tar.xz...
downloading lzo-2.10-2-armv7h.pkg.tar.xz...
downloading js52-52.9.0-2-armv7h.pkg.tar.xz...
downloading polkit-0.115+24+g5230646-1-armv7h.pkg.tar.xz...
downloading dbus-glib-0.110-1-armv7h.pkg.tar.xz...
downloading python2-2.7.16-1-armv7h.pkg.tar.xz...
downloading gconf-3.2.6+11+g07808097-4-armv7h.pkg.tar.xz...
downloading atk-2.32-1-armv7h.pkg.tar.xz...
downloading libdatrie-0.2.12-1-armv7h.pkg.tar.xz...
downloading libthai-0.1.28-1-armv7h.pkg.tar.xz...
downloading libpng-1.6.36-1-armv7h.pkg.tar.xz...
downloading xcb-proto-1.13-2-any.pkg.tar.xz...
downloading xorgproto-2018.4-1-any.pkg.tar.xz...
downloading libxdmcp-1.1.3-1-armv7h.pkg.tar.xz...
downloading libxau-1.0.9-1-armv7h.pkg.tar.xz...
downloading libxcb-1.13.1-1-armv7h.pkg.tar.xz...
downloading libx11-1.6.7-1-armv7h.pkg.tar.xz...
downloading libxrender-0.9.10-2-armv7h.pkg.tar.xz...
downloading libxext-1.3.4-1-armv7h.pkg.tar.xz...
downloading graphite-1:1.3.13-1-armv7h.pkg.tar.xz...
downloading harfbuzz-2.3.1-2-armv7h.pkg.tar.xz...
downloading freetype2-2.10.0-1-armv7h.pkg.tar.xz...
downloading fontconfig-2:2.13.1+12+g5f5ec56-1-armv7h.pkg.tar.xz...
downloading pixman-0.38.0-2-armv7h.pkg.tar.xz...
downloading cairo-1.16.0-2-armv7h.pkg.tar.xz...
downloading libxft-2.3.3-1-armv7h.pkg.tar.xz...
downloading fribidi-1.0.5-1-armv7h.pkg.tar.xz...
downloading pango-1:1.43.0-1-armv7h.pkg.tar.xz...
downloading libxfixes-5.0.3-2-armv7h.pkg.tar.xz...
downloading libxcursor-1.2.0-1-armv7h.pkg.tar.xz...
downloading libxinerama-1.1.4-1-armv7h.pkg.tar.xz...
downloading libxrandr-1.5.2-1-armv7h.pkg.tar.xz...
downloading libxi-1.7.9-2-armv7h.pkg.tar.xz...
downloading libxcomposite-0.4.5-1-armv7h.pkg.tar.xz...
downloading libxdamage-1.1.5-1-armv7h.pkg.tar.xz...
downloading shared-mime-info-1.12-1-armv7h.pkg.tar.xz...
downloading libjpeg-turbo-2.0.2-1-armv7h.pkg.tar.xz...
downloading libtiff-4.0.10-1-armv7h.pkg.tar.xz...
downloading libdaemon-0.14-4-armv7h.pkg.tar.xz...
downloading avahi-0.7+18+g1b5f401-1-armv7h.pkg.tar.xz...
downloading libcups-2.2.11-1-armv7h.pkg.tar.xz...
downloading jasper-2.0.16-1-armv7h.pkg.tar.xz...
downloading gdk-pixbuf2-2.38.1-1-armv7h.pkg.tar.xz...
downloading librsvg-2:2.44.13-1-armv7h.pkg.tar.xz...
downloading hicolor-icon-theme-0.17-1-any.pkg.tar.xz...
downloading gtk-update-icon-cache-1:3.24.7+25+g17665f06e3-1-armv7h.pkg.tar.xz...
downloading desktop-file-utils-0.23+4+g92af410-1-armv7h.pkg.tar.xz...
downloading gtk2-2.24.32-1-armv7h.pkg.tar.xz...
downloading valgrind-3.14.0-1-armv7h.pkg.tar.xz...
checking keyring...
checking package integrity...
loading package files...
checking for file conflicts...
checking available disk space...
:: Processing package changes...
installing js52...
installing polkit...
installing dbus-glib...
installing libnsl...
installing python2...
Optional dependencies for python2
    tk: for IDLE
    python2-setuptools
    python2-pip
installing gconf...
installing atk...
installing libdatrie...
installing libthai...
installing libpng...
installing xcb-proto...
installing xorgproto...
installing libxdmcp...
installing libxau...
installing libxcb...
installing libx11...
installing libxrender...
installing libxext...
installing graphite...
installing harfbuzz...
Optional dependencies for harfbuzz
    cairo: hb-view program [pending]
installing freetype2...
installing fontconfig...
  
  Fontconfig configuration is done via /etc/fonts/conf.avail and conf.d.
  Read /etc/fonts/conf.d/README for more information.

  Configuration via /etc/fonts/local.conf is still possible,
  but is no longer recommended for options available in conf.avail.

  Main systemwide configuration should be done by symlinks
  (especially for autohinting, sub-pixel and lcdfilter):
  
  cd /etc/fonts/conf.d
  ln -s ../conf.avail/XX-foo.conf
  
  Check also https://wiki.archlinux.org/index.php/Font_Configuration
  and https://wiki.archlinux.org/index.php/Fonts.

Rebuilding fontconfig cache... done.
installing pixman...
installing lzo...
installing cairo...
installing libxft...
installing fribidi...
installing pango...
installing libxfixes...
installing libxcursor...
Optional dependencies for libxcursor
    gnome-themes-standard: fallback icon theme
installing libxinerama...
installing libxrandr...
installing libxi...
installing libxcomposite...
installing libxdamage...
installing shared-mime-info...
installing libjpeg-turbo...
installing libtiff...
Optional dependencies for libtiff
    freeglut: for using tiffgt
installing libdaemon...
installing avahi...
Optional dependencies for avahi
    gtk3: avahi-discover, avahi-discover-standalone, bshell, bssh, bvnc
    gtk2: gtk2 bindings [pending]
    qt4: qt4 bindings
    qt5-base: qt5 bindings
    pygtk: avahi-bookmarks
    python2-twisted: avahi-bookmarks
    mono: mono bindings
    nss-mdns: NSS support for mDNS
    python-gobject: avahi-discover
    python-dbus: avahi-discover
installing libcups...
installing jasper...
Optional dependencies for jasper
    jasper-doc: documentation
    freeglut: jiv support
    glu: jiv support
installing gdk-pixbuf2...
installing librsvg...
installing hicolor-icon-theme...
installing gtk-update-icon-cache...
installing desktop-file-utils...
installing gtk2...
Optional dependencies for gtk2
    gnome-themes-standard: Default widget theme
    adwaita-icon-theme: Default icon theme
installing valgrind...
Optional dependencies for valgrind
    openmpi: MPI support
:: Running post-transaction hooks...
(1/9) Probing GDK-Pixbuf loader modules...
(2/9) Updating GIO module cache...
(3/9) Probing GTK2 input method modules...
(4/9) Updating icon theme caches...
(5/9) Reloading system manager configuration...
  Skipped: Current root is not booted.
(6/9) Creating system user accounts...
Creating group avahi with gid 977.
Creating user avahi (Avahi mDNS/DNS-SD daemon) with uid 977 and gid 977.
Creating group polkitd with gid 102.
Creating user polkitd (PolicyKit daemon) with uid 102 and gid 102.
(7/9) Arming ConditionNeedsUpdate...
(8/9) Updating the desktop file MIME type cache...
(9/9) Updating the MIME type database...
==> Checking buildtime dependencies...
==> Installing missing dependencies...
resolving dependencies...
looking for conflicting packages...

Packages (24) autoconf-archive-1:2019.01.06-1  boost-libs-1.69.0-1  docbook-xml-4.5-8  docbook-xsl-1.79.2-5  glib2-docs-2.60.0-1  gtk-doc-1.29-1  intltool-0.51.0-4  itstool-1:2.0.2+5+g676f3f7-1  libxslt-1.1.33-1  mallard-ducktype-0.4-1  perl-xml-parser-2.44-7  python-3.7.2-3  python-anytree-2.6.0-2  python-appdirs-1.4.3-2  python-lxml-4.3.3-1  python-packaging-19.0-1  python-pygments-2.3.1-1  python-pyparsing-2.3.1-1  python-setuptools-1:40.8.0-1  python-six-1.12.0-1  source-highlight-3.1.8-18  yelp-tools-3.32.0-1  yelp-xsl-3.32.1-1  gnome-common-3.18.0-3

Total Download Size:    23.57 MiB
Total Installed Size:  171.98 MiB

:: Proceed with installation? [Y/n] 
:: Retrieving packages...
downloading glib2-docs-2.60.0-1-armv7h.pkg.tar.xz...
downloading perl-xml-parser-2.44-7-armv7h.pkg.tar.xz...
downloading intltool-0.51.0-4-any.pkg.tar.xz...
downloading yelp-xsl-3.32.1-1-any.pkg.tar.xz...
downloading libxslt-1.1.33-1-armv7h.pkg.tar.xz...
downloading docbook-xml-4.5-8-any.pkg.tar.xz...
downloading itstool-1:2.0.2+5+g676f3f7-1-any.pkg.tar.xz...
downloading docbook-xsl-1.79.2-5-any.pkg.tar.xz...
downloading python-3.7.2-3-armv7h.pkg.tar.xz...
downloading mallard-ducktype-0.4-1-any.pkg.tar.xz...
downloading yelp-tools-3.32.0-1-any.pkg.tar.xz...
downloading boost-libs-1.69.0-1-armv7h.pkg.tar.xz...
downloading source-highlight-3.1.8-18-armv7h.pkg.tar.xz...
downloading python-lxml-4.3.3-1-armv7h.pkg.tar.xz...
downloading python-appdirs-1.4.3-2-any.pkg.tar.xz...
downloading python-pyparsing-2.3.1-1-any.pkg.tar.xz...
downloading python-six-1.12.0-1-any.pkg.tar.xz...
downloading python-packaging-19.0-1-any.pkg.tar.xz...
downloading python-setuptools-1:40.8.0-1-any.pkg.tar.xz...
downloading python-anytree-2.6.0-2-any.pkg.tar.xz...
downloading gtk-doc-1.29-1-any.pkg.tar.xz...
downloading gnome-common-3.18.0-3-any.pkg.tar.xz...
downloading autoconf-archive-1:2019.01.06-1-any.pkg.tar.xz...
downloading python-pygments-2.3.1-1-any.pkg.tar.xz...
checking keyring...
checking package integrity...
loading package files...
checking for file conflicts...
checking available disk space...
:: Processing package changes...
installing autoconf-archive...
Optional dependencies for autoconf-archive
    automake: macros for use with it [installed]
installing perl-xml-parser...
installing intltool...
installing yelp-xsl...
installing libxslt...
installing docbook-xml...
installing itstool...
installing docbook-xsl...
installing python...
Optional dependencies for python
    python-setuptools [pending]
    python-pip
    sqlite [installed]
    mpdecimal: for decimal
    xz: for lzma [installed]
    tk: for tkinter
installing mallard-ducktype...
installing yelp-tools...
installing boost-libs...
Optional dependencies for boost-libs
    openmpi: for mpi support
installing source-highlight...
installing glib2-docs...
installing python-lxml...
Optional dependencies for python-lxml
    python-beautifulsoup4: support for beautifulsoup parser to parse not well formed HTML
    python-cssselect: support for cssselect
    python-html5lib: support for html5lib parser
    python-lxml-docs: offline docs
installing python-appdirs...
installing python-pyparsing...
installing python-six...
installing python-packaging...
installing python-setuptools...
installing python-pygments...
installing python-anytree...
installing gtk-doc...
Optional dependencies for gtk-doc
    dblatex: PDF support
installing gnome-common...
:: Running post-transaction hooks...
(1/3) Warn about old perl modules
(2/3) Arming ConditionNeedsUpdate...
(3/3) Updating the info directory file...
==> Retrieving sources...
  -> Found alleyoop-0.9.8.tar.gz
  -> Found alleyoop16.png
  -> Found alleyoop32.png
  -> Found alleyoop64.png
  -> Found alleyoop128.png
  -> Found alleyoop256.png
  -> Found git-fixes.patch
==> WARNING: Skipping all source file integrity checks.
==> Extracting sources...
  -> Extracting alleyoop-0.9.8.tar.gz with bsdtar
==> Starting prepare()...
patching file ChangeLog
patching file Makefile.am
patching file acconfig.h
patching file alleyoop.desktop.in
patching file alleyoop.glade
patching file alleyoop.gladep
patching file autogen.sh
patching file configure.ac (renamed from configure.in)
patching file m4/Makefile.am
patching file m4/codeset.m4
patching file m4/gettext.m4
patching file m4/glibc21.m4
patching file m4/iconv.m4
patching file m4/intltool.m4
patching file m4/lcmessage.m4
patching file m4/progtest.m4
patching file src/Makefile.am
patching file src/alleyoop.c
patching file src/alleyoop.h
patching file src/getopts.c
patching file src/getopts.h
patching file src/legolas.c
patching file src/legolas.h
patching file src/list.c
patching file src/list.h
patching file src/main.c
patching file src/menu-utils.c
patching file src/menu-utils.h
patching file src/parser.c
patching file src/parser.h
patching file src/prefs.c
patching file src/prefs.h
patching file src/process.c
patching file src/process.h
patching file src/vgcachegrindprefs.c
patching file src/vgcachegrindprefs.h
patching file src/vgdefaultview.c
patching file src/vgdefaultview.h
patching file src/vgerror.c
patching file src/vgerror.h
patching file src/vggeneralprefs.c
patching file src/vggeneralprefs.h
patching file src/vghelgrindprefs.c
patching file src/vghelgrindprefs.h
patching file src/vgio.c
patching file src/vgio.h
patching file src/vgmemcheckprefs.c
patching file src/vgmemcheckprefs.h
patching file src/vgrule-editor.c
patching file src/vgrule-editor.h
patching file src/vgrule-list.c
patching file src/vgrule-list.h
patching file src/vgrule.c
patching file src/vgrule.h
patching file src/vgrulepattern.c
patching file src/vgrulepattern.h
patching file src/vgsearchbar.c
patching file src/vgsearchbar.h
patching file src/vgstrpool.c
patching file src/vgstrpool.h
patching file src/vgtoolprefs.c
patching file src/vgtoolprefs.h
patching file src/vgtoolview.c
patching file src/vgtoolview.h
/usr/bin/gnome-autogen.sh
***Warning*** USE_GNOME2_MACROS is deprecated, you may remove it from autogen.sh
***Warning*** PKG_NAME is deprecated, you may remove it from autogen.sh
aclocal.m4:16: warning: this file was generated for autoconf 2.68.
You have another version of autoconf.  It may work, but is not guaranteed to.
If you have problems, you may need to regenerate the build system entirely.
To do so, use the procedure documented by the package, typically `autoreconf'.
checking for automake >= 1.11.2...
  testing automake... found 1.16.1
checking for autoreconf >= 2.53...
  testing autoreconf... found 2.69
checking for glib-gettext >= 2.2.0...
  testing glib-gettextize... found 2.60.0
checking for intltool >= 0.25...
  testing intltoolize... found 0.51.0
checking for pkg-config >= 0.14.0...
  testing pkg-config... found 1.6.0
Checking for required M4 macros...
**Warning**: I am going to run `configure' with no arguments.
If you wish to pass any to it, please specify them on the
`./autogen.sh' command line.

Processing ./configure.ac
aclocal.m4:16: warning: this file was generated for autoconf 2.68.
You have another version of autoconf.  It may work, but is not guaranteed to.
If you have problems, you may need to regenerate the build system entirely.
To do so, use the procedure documented by the package, typically `autoreconf'.
Running glib-gettextize... Ignore non-fatal messages.
Copying file po/Makefile.in.in

Please add the files
  codeset.m4 gettext.m4 glibc21.m4 iconv.m4 isc-posix.m4 lcmessage.m4
  progtest.m4
from the /usr/share/aclocal directory to your autoconf macro directory
or directly to your aclocal.m4 file.
You will also need config.guess and config.sub, which you can get from
ftp://ftp.gnu.org/pub/gnu/config/.

Running intltoolize...
Running autoreconf...
autoreconf: Entering directory `.'
autoreconf: configure.ac: not using Gettext
autoreconf: running: aclocal --force --warnings=no-portability -I m4 ${ACLOCAL_FLAGS}
autoreconf: configure.ac: tracing
autoreconf: configure.ac: not using Libtool
autoreconf: running: /usr/bin/autoconf --force --warnings=no-portability
autoreconf: running: /usr/bin/autoheader --force --warnings=no-portability
autoreconf: running: automake --add-missing --copy --force-missing --warnings=no-portability
configure.ac:18: installing './compile'
src/Makefile.am:3: warning: 'INCLUDES' is the old name for 'AM_CPPFLAGS' (or '*_CPPFLAGS')
autoreconf: Leaving directory `.'
Running ./configure --enable-maintainer-mode ...
checking build system type... armv7l-unknown-linux-gnueabihf
checking host system type... armv7l-unknown-linux-gnueabihf
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /usr/bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking whether to enable maintainer-specific portions of Makefiles... yes
checking whether make supports nested variables... (cached) yes
checking for gcc... gcc
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 gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking whether gcc understands -c and -o together... yes
checking whether make supports the include directive... yes (GNU style)
checking dependency style of gcc... gcc3
checking whether ln -s works... yes
checking whether make sets $(MAKE)... (cached) yes
checking whether NLS is requested... yes
checking for intltool >= 0.40.0... 0.51.0 found
checking for intltool-update... /usr/bin/intltool-update
checking for intltool-merge... /usr/bin/intltool-merge
checking for intltool-extract... /usr/bin/intltool-extract
checking for xgettext... /usr/bin/xgettext
checking for msgmerge... /usr/bin/msgmerge
checking for msgfmt... /usr/bin/msgfmt
checking for gmsgfmt... /usr/bin/msgfmt
checking for perl... /usr/bin/perl
checking for perl >= 5.8.1... 5.28.1
checking for XML::Parser... ok
checking how to run the C preprocessor... gcc -E
checking for grep that handles long lines and -e... /usr/bin/grep
checking for egrep... /usr/bin/grep -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 locale.h usability... yes
checking locale.h presence... yes
checking for locale.h... yes
checking for LC_MESSAGES... yes
checking for CFPreferencesCopyAppValue... no
checking for CFLocaleCopyCurrent... no
checking libintl.h usability... yes
checking libintl.h presence... yes
checking for libintl.h... yes
checking for ngettext in libc... yes
checking for dgettext in libc... yes
checking for bind_textdomain_codeset... yes
checking for msgfmt... (cached) /usr/bin/msgfmt
checking for dcgettext... yes
checking if msgfmt accepts -c... yes
checking for gmsgfmt... (cached) /usr/bin/msgfmt
checking for xgettext... (cached) /usr/bin/xgettext
checking for valgrind... /usr/bin/valgrind
checking for ldd... /usr/bin/ldd
checking for emacsclient... emacsclient
checking for emacs... emacs
checking for xemacs... xemacs
checking for gvim... gvim
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.16... yes
checking for GLIB... yes
checking for GLIB - version >= 2.0.0... yes (version 2.60.0)
checking for gconftool-2... /usr/bin/gconftool-2
Using config source xml:merged:/etc/gconf/gconf.xml.defaults for schema installation
Using $(sysconfdir)/gconf/schemas as install directory for schema files
checking for ALLEYOOP... yes
checking that generated files are newer than configure... done
configure: creating ./config.status
config.status: creating Makefile
config.status: creating src/Makefile
config.status: creating po/Makefile.in
config.status: creating m4/Makefile
config.status: creating config.h
config.status: executing depfiles commands
config.status: executing default-1 commands
config.status: executing po/stamp-it commands
Now type `make' to compile alleyoop
==> Starting build()...
checking build system type... armv7l-unknown-linux-gnueabihf
checking host system type... armv7l-unknown-linux-gnueabihf
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /usr/bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking whether to enable maintainer-specific portions of Makefiles... yes
checking whether make supports nested variables... (cached) yes
checking for gcc... gcc
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 gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking whether gcc understands -c and -o together... yes
checking whether make supports the include directive... yes (GNU style)
checking dependency style of gcc... gcc3
checking whether ln -s works... yes
checking whether make sets $(MAKE)... (cached) yes
checking whether NLS is requested... yes
checking for intltool >= 0.40.0... 0.51.0 found
checking for intltool-update... /usr/bin/intltool-update
checking for intltool-merge... /usr/bin/intltool-merge
checking for intltool-extract... /usr/bin/intltool-extract
checking for xgettext... /usr/bin/xgettext
checking for msgmerge... /usr/bin/msgmerge
checking for msgfmt... /usr/bin/msgfmt
checking for gmsgfmt... /usr/bin/msgfmt
checking for perl... /usr/bin/perl
checking for perl >= 5.8.1... 5.28.1
checking for XML::Parser... ok
checking how to run the C preprocessor... gcc -E
checking for grep that handles long lines and -e... /usr/bin/grep
checking for egrep... /usr/bin/grep -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 locale.h usability... yes
checking locale.h presence... yes
checking for locale.h... yes
checking for LC_MESSAGES... yes
checking for CFPreferencesCopyAppValue... no
checking for CFLocaleCopyCurrent... no
checking libintl.h usability... yes
checking libintl.h presence... yes
checking for libintl.h... yes
checking for ngettext in libc... yes
checking for dgettext in libc... yes
checking for bind_textdomain_codeset... yes
checking for msgfmt... (cached) /usr/bin/msgfmt
checking for dcgettext... yes
checking if msgfmt accepts -c... yes
checking for gmsgfmt... (cached) /usr/bin/msgfmt
checking for xgettext... (cached) /usr/bin/xgettext
checking for valgrind... /usr/bin/valgrind
checking for ldd... /usr/bin/ldd
checking for emacsclient... emacsclient
checking for emacs... emacs
checking for xemacs... xemacs
checking for gvim... gvim
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.16... yes
checking for GLIB... yes
checking for GLIB - version >= 2.0.0... yes (version 2.60.0)
checking for gconftool-2... /usr/bin/gconftool-2
Using config source xml:merged:/etc/gconf/gconf.xml.defaults for schema installation
Using /usr/share/gconf/schemas as install directory for schema files
checking for ALLEYOOP... yes
checking that generated files are newer than configure... done
configure: creating ./config.status
config.status: creating Makefile
config.status: creating src/Makefile
config.status: creating po/Makefile.in
config.status: creating m4/Makefile
config.status: creating config.h
config.status: config.h is unchanged
config.status: executing depfiles commands
config.status: executing default-1 commands
config.status: executing po/stamp-it commands
make  all-recursive
make[1]: Entering directory '/build/alleyoop/src/alleyoop-0.9.8'
Making all in src
make[2]: Entering directory '/build/alleyoop/src/alleyoop-0.9.8/src'
make  all-am
make[3]: Entering directory '/build/alleyoop/src/alleyoop-0.9.8/src'
  CC       alleyoop.o
  CC       getopts.o
  CC       legolas.o
  CC       list.o
  CC       menu-utils.o
  CC       parser.o
  CC       prefs.o
  CC       process.o
  CC       vgcachegrindprefs.o
  CC       vgdefaultview.o
  CC       vgerror.o
alleyoop.c: In function 'alleyoop_kill':
alleyoop.c:822:3: warning: 'g_io_channel_close' is deprecated: Use 'g_io_channel_shutdown' instead [-Wdeprecated-declarations]
In file included from /usr/include/glib-2.0/glib.h:54,
                 from alleyoop.c:33:
/usr/include/glib-2.0/glib/giochannel.h:183:6: note: declared here
 void      g_io_channel_close    (GIOChannel    *channel);
      ^~~~~~~~~~~~~~~~~~
  CC       vggeneralprefs.o
  CC       vghelgrindprefs.o
  CC       vgio.o
  CC       vgmarshal.o
  CC       vgmemcheckprefs.o
  CC       vgrule.o
  CC       vgrule-editor.o
  CC       vgrule-list.o
  CC       vgrulepattern.o
  CC       vgsearchbar.o
  CC       vgstrpool.o
  CC       vgtoolprefs.o
vgrule-editor.c: In function 'vg_rule_editor_save':
vgrule-editor.c:546:3: warning: ignoring return value of 'ftruncate', declared with attribute warn_unused_result [-Wunused-result]
  CC       vgtoolview.o
  CC       main.o
vgrule-list.c: In function 'vg_rule_list_destroy':
vgrule-list.c:457:3: warning: 'g_io_channel_close' is deprecated: Use 'g_io_channel_shutdown' instead [-Wdeprecated-declarations]
In file included from /usr/include/glib-2.0/glib.h:54,
                 from vgrule-list.c:32:
/usr/include/glib-2.0/glib/giochannel.h:183:6: note: declared here
 void      g_io_channel_close    (GIOChannel    *channel);
      ^~~~~~~~~~~~~~~~~~
vgrule-list.c: In function 'load_rules_step_cb':
vgrule-list.c:504:2: warning: 'g_io_channel_close' is deprecated: Use 'g_io_channel_shutdown' instead [-Wdeprecated-declarations]
In file included from /usr/include/glib-2.0/glib.h:54,
                 from vgrule-list.c:32:
/usr/include/glib-2.0/glib/giochannel.h:183:6: note: declared here
 void      g_io_channel_close    (GIOChannel    *channel);
      ^~~~~~~~~~~~~~~~~~
vgrule-list.c: In function 'vg_rule_list_set_filename':
vgrule-list.c:569:4: warning: 'g_io_channel_close' is deprecated: Use 'g_io_channel_shutdown' instead [-Wdeprecated-declarations]
In file included from /usr/include/glib-2.0/glib.h:54,
                 from vgrule-list.c:32:
/usr/include/glib-2.0/glib/giochannel.h:183:6: note: declared here
 void      g_io_channel_close    (GIOChannel    *channel);
      ^~~~~~~~~~~~~~~~~~
  CCLD     alleyoop
make[3]: Leaving directory '/build/alleyoop/src/alleyoop-0.9.8/src'
make[2]: Leaving directory '/build/alleyoop/src/alleyoop-0.9.8/src'
Making all in po
make[2]: Entering directory '/build/alleyoop/src/alleyoop-0.9.8/po'
  MSGFMT ar.gmo
  MSGFMT az.gmo
  MSGFMT ca.gmo
  MSGFMT cs.gmo
  MSGFMT da.gmo
  MSGFMT de.gmo
  MSGFMT dz.gmo
  MSGFMT el.gmo
  MSGFMT en_CA.gmo
  MSGFMT en_GB.gmo
  MSGFMT eo.gmo
  MSGFMT es.gmo
  MSGFMT eu.gmo
  MSGFMT fi.gmo
  MSGFMT fr.gmo
  MSGFMT ga.gmo
  MSGFMT gl.gmo
  MSGFMT gu.gmo
  MSGFMT hr.gmo
  MSGFMT hu.gmo
  MSGFMT id.gmo
  MSGFMT it.gmo
  MSGFMT ja.gmo
  MSGFMT lv.gmo
  MSGFMT mk.gmo
  MSGFMT ml.gmo
  MSGFMT mn.gmo
  MSGFMT ms.gmo
  MSGFMT nb.gmo
  MSGFMT ne.gmo
  MSGFMT nl.gmo
  MSGFMT oc.gmo
  MSGFMT pa.gmo
  MSGFMT pl.gmo
  MSGFMT pt.gmo
  MSGFMT pt_BR.gmo
  MSGFMT ro.gmo
  MSGFMT ru.gmo
  MSGFMT rw.gmo
  MSGFMT sk.gmo
  MSGFMT sl.gmo
  MSGFMT sr.gmo
  MSGFMT sq.gmo
  MSGFMT sr@latin.gmo
  MSGFMT sv.gmo
  MSGFMT tr.gmo
  MSGFMT uk.gmo
  MSGFMT vi.gmo
  MSGFMT zh_CN.gmo
make[2]: Leaving directory '/build/alleyoop/src/alleyoop-0.9.8/po'
Making all in m4
make[2]: Entering directory '/build/alleyoop/src/alleyoop-0.9.8/m4'
make[2]: Nothing to be done for 'all'.
make[2]: Leaving directory '/build/alleyoop/src/alleyoop-0.9.8/m4'
make[2]: Entering directory '/build/alleyoop/src/alleyoop-0.9.8'
  ITMRG  alleyoop.desktop
make[2]: Leaving directory '/build/alleyoop/src/alleyoop-0.9.8'
make[1]: Leaving directory '/build/alleyoop/src/alleyoop-0.9.8'
==> Entering fakeroot environment...
==> Starting package()...
make: Entering directory '/build/alleyoop/src/alleyoop-0.9.8'
Making install in src
make[1]: Entering directory '/build/alleyoop/src/alleyoop-0.9.8/src'
make  install-am
make[2]: Entering directory '/build/alleyoop/src/alleyoop-0.9.8/src'
make[3]: Entering directory '/build/alleyoop/src/alleyoop-0.9.8/src'
GCONF_CONFIG_SOURCE=xml:merged:/etc/gconf/gconf.xml.defaults /usr/bin/gconftool-2 --makefile-install-rule ./alleyoop.schemas
 /usr/bin/mkdir -p '/build/alleyoop/pkg/alleyoop/usr/bin'
 /usr/bin/mkdir -p '/build/alleyoop/pkg/alleyoop/usr/share/gconf/schemas'
 /usr/bin/install -c -m 644 alleyoop.schemas '/build/alleyoop/pkg/alleyoop/usr/share/gconf/schemas'
Attached schema `/schemas/apps/alleyoop/editor' to key `/apps/alleyoop/editor'
WARNING: failed to install schema `/schemas/apps/alleyoop/editor', locale `C': Unable to store a value at key '/schemas/apps/alleyoop/editor', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
Attached schema `/schemas/apps/alleyoop/num-lines' to key `/apps/alleyoop/num-lines'
WARNING: failed to install schema `/schemas/apps/alleyoop/num-lines', locale `C': Unable to store a value at key '/schemas/apps/alleyoop/num-lines', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
Attached schema `/schemas/apps/alleyoop/valgrind/general/demangle' to key `/apps/alleyoop/valgrind/general/demangle'
WARNING: failed to install schema `/schemas/apps/alleyoop/valgrind/general/demangle', locale `C': Unable to store a value at key '/schemas/apps/alleyoop/valgrind/general/demangle', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
Attached schema `/schemas/apps/alleyoop/valgrind/general/num-callers' to key `/apps/alleyoop/valgrind/general/num-callers'
WARNING: failed to install schema `/schemas/apps/alleyoop/valgrind/general/num-callers', locale `C': Unable to store a value at key '/schemas/apps/alleyoop/valgrind/general/num-callers', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
Attached schema `/schemas/apps/alleyoop/valgrind/general/error-limit' to key `/apps/alleyoop/valgrind/general/error-limit'
WARNING: failed to install schema `/schemas/apps/alleyoop/valgrind/general/error-limit', locale `C': Unable to store a value at key '/schemas/apps/alleyoop/valgrind/general/error-limit', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
Attached schema `/schemas/apps/alleyoop/valgrind/general/sloppy-malloc' to key `/apps/alleyoop/valgrind/general/sloppy-malloc'
WARNING: failed to install schema `/schemas/apps/alleyoop/valgrind/general/sloppy-malloc', locale `C': Unable to store a value at key '/schemas/apps/alleyoop/valgrind/general/sloppy-malloc', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
Attached schema `/schemas/apps/alleyoop/valgrind/general/alignment' to key `/apps/alleyoop/valgrind/general/alignment'
WARNING: failed to install schema `/schemas/apps/alleyoop/valgrind/general/alignment', locale `C': Unable to store a value at key '/schemas/apps/alleyoop/valgrind/general/alignment', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
Attached schema `/schemas/apps/alleyoop/valgrind/general/trace-children' to key `/apps/alleyoop/valgrind/general/trace-children'
WARNING: failed to install schema `/schemas/apps/alleyoop/valgrind/general/trace-children', locale `C': Unable to store a value at key '/schemas/apps/alleyoop/valgrind/general/trace-children', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
Attached schema `/schemas/apps/alleyoop/valgrind/general/track-fds' to key `/apps/alleyoop/valgrind/general/track-fds'
WARNING: failed to install schema `/schemas/apps/alleyoop/valgrind/general/track-fds', locale `C': Unable to store a value at key '/schemas/apps/alleyoop/valgrind/general/track-fds', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
Attached schema `/schemas/apps/alleyoop/valgrind/general/track-origins' to key `/apps/alleyoop/valgrind/general/track-origins'
WARNING: failed to install schema `/schemas/apps/alleyoop/valgrind/general/track-origins', locale `C': Unable to store a value at key '/schemas/apps/alleyoop/valgrind/general/track-origins', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
Attached schema `/schemas/apps/alleyoop/valgrind/general/time-stamp' to key `/apps/alleyoop/valgrind/general/time-stamp'
WARNING: failed to install schema `/schemas/apps/alleyoop/valgrind/general/time-stamp', locale `C': Unable to store a value at key '/schemas/apps/alleyoop/valgrind/general/time-stamp', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
Attached schema `/schemas/apps/alleyoop/valgrind/general/suppressions' to key `/apps/alleyoop/valgrind/general/suppressions'
WARNING: failed to install schema `/schemas/apps/alleyoop/valgrind/general/suppressions', locale `C': Unable to store a value at key '/schemas/apps/alleyoop/valgrind/general/suppressions', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
Attached schema `/schemas/apps/alleyoop/valgrind/general/run-libc-freeres' to key `/apps/alleyoop/valgrind/general/run-libc-freeres'
WARNING: failed to install schema `/schemas/apps/alleyoop/valgrind/general/run-libc-freeres', locale `C': Unable to store a value at key '/schemas/apps/alleyoop/valgrind/general/run-libc-freeres', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
Attached schema `/schemas/apps/alleyoop/valgrind/memcheck/leak-check' to key `/apps/alleyoop/valgrind/memcheck/leak-check'
WARNING: failed to install schema `/schemas/apps/alleyoop/valgrind/memcheck/leak-check', locale `C': Unable to store a value at key '/schemas/apps/alleyoop/valgrind/memcheck/leak-check', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
Attached schema `/schemas/apps/alleyoop/valgrind/memcheck/show-reachable' to key `/apps/alleyoop/valgrind/memcheck/show-reachable'
WARNING: failed to install schema `/schemas/apps/alleyoop/valgrind/memcheck/show-reachable', locale `C': Unable to store a value at key '/schemas/apps/alleyoop/valgrind/memcheck/show-reachable', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
Attached schema `/schemas/apps/alleyoop/valgrind/memcheck/leak-resolution' to key `/apps/alleyoop/valgrind/memcheck/leak-resolution'
WARNING: failed to install schema `/schemas/apps/alleyoop/valgrind/memcheck/leak-resolution', locale `C': Unable to store a value at key '/schemas/apps/alleyoop/valgrind/memcheck/leak-resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
Attached schema `/schemas/apps/alleyoop/valgrind/memcheck/freelist-vol' to key `/apps/alleyoop/valgrind/memcheck/freelist-vol'
WARNING: failed to install schema `/schemas/apps/alleyoop/valgrind/memcheck/freelist-vol', locale `C': Unable to store a value at key '/schemas/apps/alleyoop/valgrind/memcheck/freelist-vol', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
Attached schema `/schemas/apps/alleyoop/valgrind/memcheck/ignore-ranges' to key `/apps/alleyoop/valgrind/memcheck/ignore-ranges'
WARNING: failed to install schema `/schemas/apps/alleyoop/valgrind/memcheck/ignore-ranges', locale `C': Unable to store a value at key '/schemas/apps/alleyoop/valgrind/memcheck/ignore-ranges', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
Attached schema `/schemas/apps/alleyoop/valgrind/memcheck/malloc-fill' to key `/apps/alleyoop/valgrind/memcheck/malloc-fill'
WARNING: failed to install schema `/schemas/apps/alleyoop/valgrind/memcheck/malloc-fill', locale `C': Unable to store a value at key '/schemas/apps/alleyoop/valgrind/memcheck/malloc-fill', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
Attached schema `/schemas/apps/alleyoop/valgrind/memcheck/free-fill' to key `/apps/alleyoop/valgrind/memcheck/free-fill'
WARNING: failed to install schema `/schemas/apps/alleyoop/valgrind/memcheck/free-fill', locale `C': Unable to store a value at key '/schemas/apps/alleyoop/valgrind/memcheck/free-fill', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
Attached schema `/schemas/apps/alleyoop/valgrind/memcheck/track-origins' to key `/apps/alleyoop/valgrind/memcheck/track-origins'
WARNING: failed to install schema `/schemas/apps/alleyoop/valgrind/memcheck/track-origins', locale `C': Unable to store a value at key '/schemas/apps/alleyoop/valgrind/memcheck/track-origins', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
Attached schema `/schemas/apps/alleyoop/valgrind/memcheck/workaround-gcc296-bugs' to key `/apps/alleyoop/valgrind/memcheck/workaround-gcc296-bugs'
WARNING: failed to install schema `/schemas/apps/alleyoop/valgrind/memcheck/workaround-gcc296-bugs', locale `C': Unable to store a value at key '/schemas/apps/alleyoop/valgrind/memcheck/workaround-gcc296-bugs', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
Attached schema `/schemas/apps/alleyoop/valgrind/cachegrind/I1/override' to key `/apps/alleyoop/valgrind/cachegrind/I1/override'
WARNING: failed to install schema `/schemas/apps/alleyoop/valgrind/cachegrind/I1/override', locale `C': Unable to store a value at key '/schemas/apps/alleyoop/valgrind/cachegrind/I1/override', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
Attached schema `/schemas/apps/alleyoop/valgrind/cachegrind/I1/settings' to key `/apps/alleyoop/valgrind/cachegrind/I1/settings'
WARNING: failed to install schema `/schemas/apps/alleyoop/valgrind/cachegrind/I1/settings', locale `C': Unable to store a value at key '/schemas/apps/alleyoop/valgrind/cachegrind/I1/settings', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
Attached schema `/schemas/apps/alleyoop/valgrind/cachegrind/D1/override' to key `/apps/alleyoop/valgrind/cachegrind/D1/override'
WARNING: failed to install schema `/schemas/apps/alleyoop/valgrind/cachegrind/D1/override', locale `C': Unable to store a value at key '/schemas/apps/alleyoop/valgrind/cachegrind/D1/override', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
Attached schema `/schemas/apps/alleyoop/valgrind/cachegrind/D1/settings' to key `/apps/alleyoop/valgrind/cachegrind/D1/settings'
WARNING: failed to install schema `/schemas/apps/alleyoop/valgrind/cachegrind/D1/settings', locale `C': Unable to store a value at key '/schemas/apps/alleyoop/valgrind/cachegrind/D1/settings', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
Attached schema `/schemas/apps/alleyoop/valgrind/cachegrind/L2/override' to key `/apps/alleyoop/valgrind/cachegrind/L2/override'
WARNING: failed to install schema `/schemas/apps/alleyoop/valgrind/cachegrind/L2/override', locale `C': Unable to store a value at key '/schemas/apps/alleyoop/valgrind/cachegrind/L2/override', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
Attached schema `/schemas/apps/alleyoop/valgrind/cachegrind/L2/settings' to key `/apps/alleyoop/valgrind/cachegrind/L2/settings'
WARNING: failed to install schema `/schemas/apps/alleyoop/valgrind/cachegrind/L2/settings', locale `C': Unable to store a value at key '/schemas/apps/alleyoop/valgrind/cachegrind/L2/settings', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
Attached schema `/schemas/apps/alleyoop/valgrind/helgrind/happens-before' to key `/apps/alleyoop/valgrind/helgrind/happens-before'
WARNING: failed to install schema `/schemas/apps/alleyoop/valgrind/helgrind/happens-before', locale `C': Unable to store a value at key '/schemas/apps/alleyoop/valgrind/helgrind/happens-before', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
Attached schema `/schemas/apps/alleyoop/valgrind/helgrind/enable-trace-addr' to key `/apps/alleyoop/valgrind/helgrind/enable-trace-addr'
WARNING: failed to install schema `/schemas/apps/alleyoop/valgrind/helgrind/enable-trace-addr', locale `C': Unable to store a value at key '/schemas/apps/alleyoop/valgrind/helgrind/enable-trace-addr', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
Attached schema `/schemas/apps/alleyoop/valgrind/helgrind/trace-addr' to key `/apps/alleyoop/valgrind/helgrind/trace-addr'
WARNING: failed to install schema `/schemas/apps/alleyoop/valgrind/helgrind/trace-addr', locale `C': Unable to store a value at key '/schemas/apps/alleyoop/valgrind/helgrind/trace-addr', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
Attached schema `/schemas/apps/alleyoop/valgrind/helgrind/trace-level' to key `/apps/alleyoop/valgrind/helgrind/trace-level'
WARNING: failed to install schema `/schemas/apps/alleyoop/valgrind/helgrind/trace-level', locale `C': Unable to store a value at key '/schemas/apps/alleyoop/valgrind/helgrind/trace-level', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
  /usr/bin/install -c alleyoop '/build/alleyoop/pkg/alleyoop/usr/bin'
make[3]: Leaving directory '/build/alleyoop/src/alleyoop-0.9.8/src'
make[2]: Leaving directory '/build/alleyoop/src/alleyoop-0.9.8/src'
make[1]: Leaving directory '/build/alleyoop/src/alleyoop-0.9.8/src'
Making install in po
make[1]: Entering directory '/build/alleyoop/src/alleyoop-0.9.8/po'
linguas="az ar ca cs da de dz el en_CA en_GB eo es eu fi fr ga gl gu hr hu id it ja lv mk ml mn ms nb ne nl oc pa pl pt pt_BR ro ru rw sk sl sq sr sr@latin sv tr uk vi zh_CN "; \
for lang in $linguas; do \
  dir=/build/alleyoop/pkg/alleyoop/usr/share/locale/$lang/LC_MESSAGES; \
  /bin/sh /build/alleyoop/src/alleyoop-0.9.8/install-sh -d $dir; \
  if test -r $lang.gmo; then \
    /usr/bin/install -c -m 644 $lang.gmo $dir/alleyoop.mo; \
    echo "installing $lang.gmo as $dir/alleyoop.mo"; \
  else \
    /usr/bin/install -c -m 644 ./$lang.gmo $dir/alleyoop.mo; \
    echo "installing ./$lang.gmo as" \
	 "$dir/alleyoop.mo"; \
  fi; \
  if test -r $lang.gmo.m; then \
    /usr/bin/install -c -m 644 $lang.gmo.m $dir/alleyoop.mo.m; \
    echo "installing $lang.gmo.m as $dir/alleyoop.mo.m"; \
  else \
    if test -r ./$lang.gmo.m ; then \
      /usr/bin/install -c -m 644 ./$lang.gmo.m \
	$dir/alleyoop.mo.m; \
      echo "installing ./$lang.gmo.m as" \
	   "$dir/alleyoop.mo.m"; \
    else \
      true; \
    fi; \
  fi; \
done
installing az.gmo as /build/alleyoop/pkg/alleyoop/usr/share/locale/az/LC_MESSAGES/alleyoop.mo
installing ar.gmo as /build/alleyoop/pkg/alleyoop/usr/share/locale/ar/LC_MESSAGES/alleyoop.mo
installing ca.gmo as /build/alleyoop/pkg/alleyoop/usr/share/locale/ca/LC_MESSAGES/alleyoop.mo
installing cs.gmo as /build/alleyoop/pkg/alleyoop/usr/share/locale/cs/LC_MESSAGES/alleyoop.mo
installing da.gmo as /build/alleyoop/pkg/alleyoop/usr/share/locale/da/LC_MESSAGES/alleyoop.mo
installing de.gmo as /build/alleyoop/pkg/alleyoop/usr/share/locale/de/LC_MESSAGES/alleyoop.mo
installing dz.gmo as /build/alleyoop/pkg/alleyoop/usr/share/locale/dz/LC_MESSAGES/alleyoop.mo
installing el.gmo as /build/alleyoop/pkg/alleyoop/usr/share/locale/el/LC_MESSAGES/alleyoop.mo
installing en_CA.gmo as /build/alleyoop/pkg/alleyoop/usr/share/locale/en_CA/LC_MESSAGES/alleyoop.mo
installing en_GB.gmo as /build/alleyoop/pkg/alleyoop/usr/share/locale/en_GB/LC_MESSAGES/alleyoop.mo
installing eo.gmo as /build/alleyoop/pkg/alleyoop/usr/share/locale/eo/LC_MESSAGES/alleyoop.mo
installing es.gmo as /build/alleyoop/pkg/alleyoop/usr/share/locale/es/LC_MESSAGES/alleyoop.mo
installing eu.gmo as /build/alleyoop/pkg/alleyoop/usr/share/locale/eu/LC_MESSAGES/alleyoop.mo
installing fi.gmo as /build/alleyoop/pkg/alleyoop/usr/share/locale/fi/LC_MESSAGES/alleyoop.mo
installing fr.gmo as /build/alleyoop/pkg/alleyoop/usr/share/locale/fr/LC_MESSAGES/alleyoop.mo
installing ga.gmo as /build/alleyoop/pkg/alleyoop/usr/share/locale/ga/LC_MESSAGES/alleyoop.mo
installing gl.gmo as /build/alleyoop/pkg/alleyoop/usr/share/locale/gl/LC_MESSAGES/alleyoop.mo
installing gu.gmo as /build/alleyoop/pkg/alleyoop/usr/share/locale/gu/LC_MESSAGES/alleyoop.mo
installing hr.gmo as /build/alleyoop/pkg/alleyoop/usr/share/locale/hr/LC_MESSAGES/alleyoop.mo
installing hu.gmo as /build/alleyoop/pkg/alleyoop/usr/share/locale/hu/LC_MESSAGES/alleyoop.mo
installing id.gmo as /build/alleyoop/pkg/alleyoop/usr/share/locale/id/LC_MESSAGES/alleyoop.mo
installing it.gmo as /build/alleyoop/pkg/alleyoop/usr/share/locale/it/LC_MESSAGES/alleyoop.mo
installing ja.gmo as /build/alleyoop/pkg/alleyoop/usr/share/locale/ja/LC_MESSAGES/alleyoop.mo
installing lv.gmo as /build/alleyoop/pkg/alleyoop/usr/share/locale/lv/LC_MESSAGES/alleyoop.mo
installing mk.gmo as /build/alleyoop/pkg/alleyoop/usr/share/locale/mk/LC_MESSAGES/alleyoop.mo
installing ml.gmo as /build/alleyoop/pkg/alleyoop/usr/share/locale/ml/LC_MESSAGES/alleyoop.mo
installing mn.gmo as /build/alleyoop/pkg/alleyoop/usr/share/locale/mn/LC_MESSAGES/alleyoop.mo
installing ms.gmo as /build/alleyoop/pkg/alleyoop/usr/share/locale/ms/LC_MESSAGES/alleyoop.mo
installing nb.gmo as /build/alleyoop/pkg/alleyoop/usr/share/locale/nb/LC_MESSAGES/alleyoop.mo
installing ne.gmo as /build/alleyoop/pkg/alleyoop/usr/share/locale/ne/LC_MESSAGES/alleyoop.mo
installing nl.gmo as /build/alleyoop/pkg/alleyoop/usr/share/locale/nl/LC_MESSAGES/alleyoop.mo
installing oc.gmo as /build/alleyoop/pkg/alleyoop/usr/share/locale/oc/LC_MESSAGES/alleyoop.mo
installing pa.gmo as /build/alleyoop/pkg/alleyoop/usr/share/locale/pa/LC_MESSAGES/alleyoop.mo
installing pl.gmo as /build/alleyoop/pkg/alleyoop/usr/share/locale/pl/LC_MESSAGES/alleyoop.mo
installing pt.gmo as /build/alleyoop/pkg/alleyoop/usr/share/locale/pt/LC_MESSAGES/alleyoop.mo
installing pt_BR.gmo as /build/alleyoop/pkg/alleyoop/usr/share/locale/pt_BR/LC_MESSAGES/alleyoop.mo
installing ro.gmo as /build/alleyoop/pkg/alleyoop/usr/share/locale/ro/LC_MESSAGES/alleyoop.mo
installing ru.gmo as /build/alleyoop/pkg/alleyoop/usr/share/locale/ru/LC_MESSAGES/alleyoop.mo
installing rw.gmo as /build/alleyoop/pkg/alleyoop/usr/share/locale/rw/LC_MESSAGES/alleyoop.mo
installing sk.gmo as /build/alleyoop/pkg/alleyoop/usr/share/locale/sk/LC_MESSAGES/alleyoop.mo
installing sl.gmo as /build/alleyoop/pkg/alleyoop/usr/share/locale/sl/LC_MESSAGES/alleyoop.mo
installing sq.gmo as /build/alleyoop/pkg/alleyoop/usr/share/locale/sq/LC_MESSAGES/alleyoop.mo
installing sr.gmo as /build/alleyoop/pkg/alleyoop/usr/share/locale/sr/LC_MESSAGES/alleyoop.mo
installing sr@latin.gmo as /build/alleyoop/pkg/alleyoop/usr/share/locale/sr@latin/LC_MESSAGES/alleyoop.mo
installing sv.gmo as /build/alleyoop/pkg/alleyoop/usr/share/locale/sv/LC_MESSAGES/alleyoop.mo
installing tr.gmo as /build/alleyoop/pkg/alleyoop/usr/share/locale/tr/LC_MESSAGES/alleyoop.mo
installing uk.gmo as /build/alleyoop/pkg/alleyoop/usr/share/locale/uk/LC_MESSAGES/alleyoop.mo
installing vi.gmo as /build/alleyoop/pkg/alleyoop/usr/share/locale/vi/LC_MESSAGES/alleyoop.mo
installing zh_CN.gmo as /build/alleyoop/pkg/alleyoop/usr/share/locale/zh_CN/LC_MESSAGES/alleyoop.mo
make[1]: Leaving directory '/build/alleyoop/src/alleyoop-0.9.8/po'
Making install in m4
make[1]: Entering directory '/build/alleyoop/src/alleyoop-0.9.8/m4'
make[2]: Entering directory '/build/alleyoop/src/alleyoop-0.9.8/m4'
make[2]: Nothing to be done for 'install-exec-am'.
make[2]: Nothing to be done for 'install-data-am'.
make[2]: Leaving directory '/build/alleyoop/src/alleyoop-0.9.8/m4'
make[1]: Leaving directory '/build/alleyoop/src/alleyoop-0.9.8/m4'
make[1]: Entering directory '/build/alleyoop/src/alleyoop-0.9.8'
make[2]: Entering directory '/build/alleyoop/src/alleyoop-0.9.8'
make[2]: Nothing to be done for 'install-exec-am'.
if test -d ./pixmaps; then \
  /bin/sh ./mkinstalldirs /build/alleyoop/pkg/alleyoop/usr/share/pixmaps/alleyoop; \
  for pixmap in ./pixmaps/*; do \
    if test -f $pixmap; then \
      /usr/bin/install -c -m 644 $pixmap /build/alleyoop/pkg/alleyoop/usr/share/pixmaps/alleyoop; \
    fi \
  done \
fi
 /usr/bin/mkdir -p '/build/alleyoop/pkg/alleyoop/usr/share/applications'
 /usr/bin/install -c -m 644 alleyoop.desktop '/build/alleyoop/pkg/alleyoop/usr/share/applications'
make[2]: Leaving directory '/build/alleyoop/src/alleyoop-0.9.8'
make[1]: Leaving directory '/build/alleyoop/src/alleyoop-0.9.8'
make: Leaving directory '/build/alleyoop/src/alleyoop-0.9.8'
==> Tidying install...
  -> Removing libtool files...
  -> Purging unwanted files...
  -> Removing static library files...
  -> Stripping unneeded symbols from binaries and libraries...
  -> Compressing man and info pages...
==> Checking for packaging issues...
==> Creating package "alleyoop"...
  -> Generating .PKGINFO file...
  -> Generating .BUILDINFO file...
  -> Generating .MTREE file...
  -> Compressing package...
==> Leaving fakeroot environment.
==> Finished making: alleyoop 0.9.8-7 (Wed 27 Mar 2019 04:19:26 PM UTC)
==> Cleaning up...