Subject: pkg/36256: security/seahorse fails to install properly (NetBSD 3.0)
To: None <pkg-manager@netbsd.org, gnats-admin@netbsd.org,>
From: None <kre@munnari.OZ.AU>
List: pkgsrc-bugs
Date: 05/02/2007 07:00:01
>Number:         36256
>Category:       pkg
>Synopsis:       security/seahorse fails to install properly (NetBSD 3.0)
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    pkg-manager
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Wed May 02 07:00:00 +0000 2007
>Originator:     Robert Elz
>Release:        NetBSD 3.99.15  (pkgsrc current within past 12 hours)
>Organization:
	Prince of Songkla University
>Environment:
System: NetBSD jade.coe.psu.ac.th 3.99.15 NetBSD 3.99.15 (GENERIC-1.696-20060125) #8: Wed Jan 25 04:59:39 ICT 2006 kre@jade.coe.psu.ac.th:/usr/obj/current/kernels/JADE_ASUS i386
Architecture: i386
Machine: i386
>Description:
	security/seahorse, late in its install phase, attemps to
	add the setuid bit (chmod u+s) to /usr/pkg/bin/seahorse-daemon
	which does not exist (has not been installed).   The chmod
	fails, and mail aborts.

>How-To-Repeat:
	I use pkg_comp and libkver with NetBSD 3.0 sets (and sources)
	installed in the sandbox.   For many packages, the compilation
	will start in a reatively empty sandbox, installing packages
	as required by the dependencies before compiling.   For
	security/seahorse all that part seems to work as it should.

	The actual error eventually reveals itself as ...


gmake[3]: Nothing to be done for `install-data-am'.
gmake[3]: Leaving directory `/pkg_comp/obj/pkgsrc/security/seahorse/default/seah
orse-1.0.1/plugins'
gmake[2]: Leaving directory `/pkg_comp/obj/pkgsrc/security/seahorse/default/seah
orse-1.0.1/plugins'
gmake[1]: Leaving directory `/pkg_comp/obj/pkgsrc/security/seahorse/default/seah
orse-1.0.1/plugins'
Making install in agent
gmake[1]: Entering directory `/pkg_comp/obj/pkgsrc/security/seahorse/default/sea
horse-1.0.1/agent'
gmake[2]: Entering directory `/pkg_comp/obj/pkgsrc/security/seahorse/default/sea
horse-1.0.1/agent'
test -z "/usr/pkg/bin" || /bin/sh ../mkinstalldirs "/usr/pkg/bin"
  /bin/sh ../libtool --mode=install /usr/bin/install -c -s -o root -g wheel -m 5
55 'seahorse-agent' '/usr/pkg/bin/seahorse-agent'
/usr/bin/install -c -o root -g wheel -m 555 -s .libs/seahorse-agent /usr/pkg/bin
/seahorse-agent
/usr/pkg/bin/gmake  install-exec-hook
gmake[3]: Entering directory `/pkg_comp/obj/pkgsrc/security/seahorse/default/sea
horse-1.0.1/agent'  
chmod u+s /usr/pkg/bin/seahorse-daemon 
chmod: /usr/pkg/bin/seahorse-daemon: No such file or directory
gmake[3]: *** [install-exec-hook] Error 1
gmake[3]: Leaving directory `/pkg_comp/obj/pkgsrc/security/seahorse/default/seah
orse-1.0.1/agent'
gmake[2]: *** [install-exec-am] Error 2
gmake[2]: Leaving directory `/pkg_comp/obj/pkgsrc/security/seahorse/default/seah
orse-1.0.1/agent'
gmake[1]: *** [install-am] Error 2
gmake[1]: Leaving directory `/pkg_comp/obj/pkgsrc/security/seahorse/default/seah
orse-1.0.1/agent' 
gmake: *** [install-recursive] Error 1
*** Error code 2

	It is worth noting (though it is possible this is simply
	noise that can be ignored - I would it hadn't been for the
	above problem) that during the configure phase ... (MUCH earlier)


checking whether to build static libraries... yes
configure: creating libtool
appending configuration tag "CXX" to libtool
checking whether the c++ linker (/pkg_comp/obj/pkgsrc/security/seahorse/default/
.wrapper/bin/ld) supports shared libraries...
[wrapper.sh] note: The real command line, after the pkgsrc wrapper, was:
/pkg_comp/obj/pkgsrc/security/seahorse/default/.compiler/bin/c++-fail-wrapper -E
 - -I/pkg_comp/obj/pkgsrc/security/seahorse/default/.buildlink/include -L/pkg_co
mp/obj/pkgsrc/security/seahorse/default/.buildlink/lib
yes
libtool.m4: error: problem compiling CXX test program
checking for c++ option to produce PIC...
checking if c++ static flag  works... no
checking if c++ supports -c -o file.o... no
checking whether the c++ linker (/pkg_comp/obj/pkgsrc/security/seahorse/default/
.wrapper/bin/ld) supports shared libraries... yes
checking dynamic linker characteristics...
[wrapper.sh] note: The real command line, after the pkgsrc wrapper, was:
/pkg_comp/obj/pkgsrc/security/seahorse/default/.compiler/bin/c++-fail-wrapper -E
 - -I/pkg_comp/obj/pkgsrc/security/seahorse/default/.buildlink/include -L/pkg_co
mp/obj/pkgsrc/security/seahorse/default/.buildlink/lib
NetBSD ld.elf_so
checking how to hardcode library paths into programs... unsupported

	[...]

checking for SOUP... yes
enabling key server support
disabling nautilus plugin
enabling password caching agent
checking for GNOME_KEYRING... yes
enabling gnome-keyring support
checking for SHARING... gnome-config: not found
gnome-config: not found
no
checking for DBUS... yes
checking for dbus-binding-tool... /usr/pkg/bin/dbus-binding-tool
checking for LIBCRYPTUI... yes
enabling epiphany plugin...
checking for gawk... (cached) /usr/bin/awk
checking which gecko to use... gnome-config: not found
gnome-config: not found
gnome-config: not found
gnome-config: not found
gnome-config: not found

disabling epiphany plugin
enabling gedit plugin...
checking for supported versions of gedit...
checking for GEDIT... gnome-config: not found
no
checking for GEDIT... gnome-config: not found
no
checking for GEDIT... gnome-config: not found
no
checking for GEDIT... gnome-config: not found
no
checking for GEDIT... gnome-config: not found
no
checking for GEDIT... gnome-config: not found
no
checking for supported versions of libpanelapplet...
checking for GNOME_APPLETS... gnome-config: not found
no
checking for LIBNOTIFY... gnome-config: not found
no
checking for ssh-keygen... /usr/bin/ssh-keygen
checking for ssh-add... /usr/bin/ssh-add
checking for ssh... /usr/bin/ssh
disabling debug compile mode

	Whether those apparently unexpected problems cause the
	evntual failure I have no idea.

>Fix:
	???