Re: port seahorse won't upgrade properly
Jeremy Messenger [EMAIL PROTECTED] wrote: On Tue, 15 Apr 2008 17:04:00 -0500, Dino Vliet wrote: Uuuhhh, ok, you've got me here, I'm LOST. What KEYRING option? I didn't recall (dis)abling any option. If you didn't tweak it then you didn't clean your ports tree before run it. I just want to install seahorse via the make install distclean command in the seahorse port directory and keep getting an error. Just tried it tonight again and this was the result: checking whether the c++ linker (/usr/bin/ld) supports shared libraries... yes checking dynamic linker characteristics... freebsd6.3 ld.so checking how to hardcode library paths into programs... immediate appending configuration tag F77 to libtool checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... no checking for f77 option to produce PIC... -fPIC checking if f77 PIC flag -fPIC works... yes checking if f77 static flag -static works... yes checking if f77 supports -c -o file.o... yes checking whether the f77 linker (/usr/bin/ld) supports shared libraries... yes checking dynamic linker characteristics... freebsd6.3 ld.so checking how to hardcode library paths into programs... immediate 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 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 for ANSI C header files... (cached) yes checking whether we are using the GNU C++ compiler... (cached) yes checking whether c++ accepts -g... (cached) yes checking dependency style of c++... (cached) gcc3 checking for glib-genmarshal... /usr/local/bin/glib-genmarshal checking for glib-mkenums... /usr/local/bin/glib-mkenums checking for intltool = 0.35.0... 0.36.2 found checking for perl... /usr/bin/perl checking for XML::Parser... ok checking for pkg-config... /usr/local/bin/pkg-config checking pkg-config is at least version 0.9.0... yes checking what warning flags to pass to the C compiler... checking what language compliance flags to pass to the C compiler... checking what warning flags to pass to the C++ compiler... -Wall -Wno-unused checking what language compliance flags to pass to the C++ compiler... checking for DEPENDENCIES... yes checking for DBUS... yes checking for dbus-binding-tool... /usr/local/bin/dbus-binding-tool Using config source xml:merged:/usr/local/etc/gconf/gconf.xml.defaults for schema installation Using $(sysconfdir)/gconf/schemas as install directory for schema files checking for gconftool-2... /usr/local/bin/gconftool-2 checking for mkdtemp... yes checking for which engine to use... mozilla checking for gawk... (cached) gawk checking which gecko to use... firefox checking manual gecko home set... checking for compiler -fshort-wchar option... yes checking whether to enable C++ RTTI... no checking whether we have a gtk 2 gecko build... yes checking whether we have a gecko debug build... no checking whether we have a xpcom glue... no checking for gecko version... 1.8.1 checking nspr in gecko... no checking nspr in system... yes checking whether we can compile and run XPCOM programs... no configure: error: Cannot compile and run XPCOM programs See `config.log' for more details. === Script configure failed unexpectedly. Please run the gnomelogalyzer, available from http://www.freebsd.org/gnome/gnomelogalyzer.sh;, which will diagnose the problem and suggest a solution. If - and only if - the gnomelogalyzer cannot solve the problem, report the build failure to the FreeBSD GNOME team at [EMAIL PROTECTED], and attach (a) /usr/ports/www/epiphany/work/epiphany-2.22.1.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 ([EMAIL PROTECTED]), because attachments sent to FreeBSD mailing lists are usually discarded by the mailing list software. *** Error code 1 Stop in /usr/ports/www/epiphany. *** Error code 1 Stop in /usr/ports/security/seahorse. *** Error code 1 Stop in /usr/ports/security/seahorse. So still no solution for seahorse. Hope you know what's wrong and how it can be solved. This is different problem now, it's not
Re: port seahorse won't upgrade properly
Jeremy Messenger [EMAIL PROTECTED] wrote: On Mon, 14 Apr 2008 13:36:18 -0500, Dino Vliet wrote: I've continued with the seahorse problem. In /usr/ports/UPDATING I couldn't find anything regarding seahorse! The gnome-keyring-manager is in /usr/ports/MOVED for gnome-keyring-manager - seahorse. For some reason, your portupgrade doesn't remove and replace to seahorse by itself. I don't know what happened. So I removed gnome-keyring-manager as you suggested. Then I did a portsnap fetch update. I then tried to install seahorse but got the following error: === epiphany-2.22.1.1 depends on shared library: ORBit-2.0 - found === epiphany-2.22.1.1 depends on shared library: pango-1.0.0 - found === Configuring for epiphany-2.22.1.1 checking what language compliance flags to pass to the C++ compiler... checking for DEPENDENCIES... configure: error: Package requirements ( glib-2.0 = 2.16.0 gmodule-2.0 gio-unix-2.0 = 2.16.0 gtk+-2.0 = 2.12.0 gtk+-unix-print-2.0 = 2.12.0 libxml-2.0 = 2.6.12 libxslt = 1.1.7 libgnome-2.0 = 2.14.0 libgnomeui-2.0 = 2.14.0 libglade-2.0 = 2.3.1 gconf-2.0 gnome-desktop-2.0 = 2.9.91 libstartup-notification-1.0 = 0.5 libnotify = 0.4 ) were not met: Package gnome-keyring-1 was not found in the pkg-config search path. Perhaps you should add the directory containing `gnome-keyring-1.pc' to the PKG_CONFIG_PATH environment variable Package 'gnome-keyring-1', required by 'libgnomeui', not found What now? I really don't have a clue. Hope you can help me out, Let me guess, you have selected to disable KEYRING option? It looks like this part is our fault. In Seahorse 2.22, it no longer provide option, which it required to have gnome-keyring dependency. I will fix it when I get back this afternoon by remove KEYRING option and depend on gnome-keyring. Meaning time, you can re-enable KEYRING and it should install Seahorse. Cheers, Mezz brgds Dino -- [EMAIL PROTECTED] - [EMAIL PROTECTED] FreeBSD GNOME Team http://www.FreeBSD.org/gnome/ - [EMAIL PROTECTED] Uuuhhh, ok, you've got me here, I'm LOST. What KEYRING option? I didn't recall (dis)abling any option. I just want to install seahorse via the make install distclean command in the seahorse port directory and keep getting an error. Just tried it tonight again and this was the result: checking whether the c++ linker (/usr/bin/ld) supports shared libraries... yes checking dynamic linker characteristics... freebsd6.3 ld.so checking how to hardcode library paths into programs... immediate appending configuration tag F77 to libtool checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... no checking for f77 option to produce PIC... -fPIC checking if f77 PIC flag -fPIC works... yes checking if f77 static flag -static works... yes checking if f77 supports -c -o file.o... yes checking whether the f77 linker (/usr/bin/ld) supports shared libraries... yes checking dynamic linker characteristics... freebsd6.3 ld.so checking how to hardcode library paths into programs... immediate 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 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 for ANSI C header files... (cached) yes checking whether we are using the GNU C++ compiler... (cached) yes checking whether c++ accepts -g... (cached) yes checking dependency style of c++... (cached) gcc3 checking for glib-genmarshal... /usr/local/bin/glib-genmarshal checking for glib-mkenums... /usr/local/bin/glib-mkenums checking for intltool = 0.35.0... 0.36.2 found checking for perl... /usr/bin/perl checking for XML::Parser... ok checking for pkg-config... /usr/local/bin/pkg-config checking pkg-config is at least version 0.9.0... yes checking what warning flags to pass to the C compiler... checking what language compliance flags to pass to the C compiler... checking what warning flags to pass to the C++ compiler... -Wall -Wno-unused checking what language compliance flags to pass to the C++ compiler... checking for DEPENDENCIES... yes checking for DBUS... yes checking for dbus-binding-tool... /usr/local/bin/dbus-binding-tool Using config source
Re: port seahorse won't upgrade properly
On Tue, 15 Apr 2008 17:04:00 -0500, Dino Vliet [EMAIL PROTECTED] wrote: Uuuhhh, ok, you've got me here, I'm LOST. What KEYRING option? I didn't recall (dis)abling any option. If you didn't tweak it then you didn't clean your ports tree before run it. I just want to install seahorse via the make install distclean command in the seahorse port directory and keep getting an error. Just tried it tonight again and this was the result: checking whether the c++ linker (/usr/bin/ld) supports shared libraries... yes checking dynamic linker characteristics... freebsd6.3 ld.so checking how to hardcode library paths into programs... immediate appending configuration tag F77 to libtool checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... no checking for f77 option to produce PIC... -fPIC checking if f77 PIC flag -fPIC works... yes checking if f77 static flag -static works... yes checking if f77 supports -c -o file.o... yes checking whether the f77 linker (/usr/bin/ld) supports shared libraries... yes checking dynamic linker characteristics... freebsd6.3 ld.so checking how to hardcode library paths into programs... immediate 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 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 for ANSI C header files... (cached) yes checking whether we are using the GNU C++ compiler... (cached) yes checking whether c++ accepts -g... (cached) yes checking dependency style of c++... (cached) gcc3 checking for glib-genmarshal... /usr/local/bin/glib-genmarshal checking for glib-mkenums... /usr/local/bin/glib-mkenums checking for intltool = 0.35.0... 0.36.2 found checking for perl... /usr/bin/perl checking for XML::Parser... ok checking for pkg-config... /usr/local/bin/pkg-config checking pkg-config is at least version 0.9.0... yes checking what warning flags to pass to the C compiler... checking what language compliance flags to pass to the C compiler... checking what warning flags to pass to the C++ compiler... -Wall -Wno-unused checking what language compliance flags to pass to the C++ compiler... checking for DEPENDENCIES... yes checking for DBUS... yes checking for dbus-binding-tool... /usr/local/bin/dbus-binding-tool Using config source xml:merged:/usr/local/etc/gconf/gconf.xml.defaults for schema installation Using $(sysconfdir)/gconf/schemas as install directory for schema files checking for gconftool-2... /usr/local/bin/gconftool-2 checking for mkdtemp... yes checking for which engine to use... mozilla checking for gawk... (cached) gawk checking which gecko to use... firefox checking manual gecko home set... checking for compiler -fshort-wchar option... yes checking whether to enable C++ RTTI... no checking whether we have a gtk 2 gecko build... yes checking whether we have a gecko debug build... no checking whether we have a xpcom glue... no checking for gecko version... 1.8.1 checking nspr in gecko... no checking nspr in system... yes checking whether we can compile and run XPCOM programs... no configure: error: Cannot compile and run XPCOM programs See `config.log' for more details. === Script configure failed unexpectedly. Please run the gnomelogalyzer, available from http://www.freebsd.org/gnome/gnomelogalyzer.sh;, which will diagnose the problem and suggest a solution. If - and only if - the gnomelogalyzer cannot solve the problem, report the build failure to the FreeBSD GNOME team at [EMAIL PROTECTED], and attach (a) /usr/ports/www/epiphany/work/epiphany-2.22.1.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 ([EMAIL PROTECTED]), because attachments sent to FreeBSD mailing lists are usually discarded by the mailing list software. *** Error code 1 Stop in /usr/ports/www/epiphany. *** Error code 1 Stop in /usr/ports/security/seahorse. *** Error code 1 Stop in /usr/ports/security/seahorse. So still no solution for seahorse. Hope you know what's wrong and how it can be solved. This is different problem now, it's not gnome-keyring anymore. This is same with your yelp problem. I have no idea how to solve with your broke
Re: port seahorse won't upgrade properly
Jeremy Messenger [EMAIL PROTECTED] wrote: On Sun, 13 Apr 2008 15:56:11 -0500, Dino Vliet wrote: Jeremy Messenger wrote: On Sat, 12 Apr 2008 14:45:47 -0500, Dino Vliet wrote: Folks, I've tried to upgrade my ports and get the following error from gnome-applets everytime I do a portupgrade gnome-applets: ain.c:42: error: structure has no member named `gconf' main.c:46: error: structure has no member named `gweather_pref' main.c:46: error: structure has no member named `gconf' gmake[2]: *** [main.o] Error 1 gmake[2]: Leaving directory `/usr/ports/x11/gnome-applets/work/gnome-applets-2.22.1/gweather' gmake[1]: *** [install-recursive] Error 1 gmake[1]: Leaving directory `/usr/ports/x11/gnome-applets/work/gnome-applets-2.22.1/gweather' gmake: *** [install-recursive] Error 1 *** Error code 2 Stop in /usr/ports/x11/gnome-applets. *** Error code 1 Stop in /usr/ports/x11/gnome-applets. *** Error code 1 Stop in /usr/ports/x11/gnome-applets. ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade.38565.0 env UPGRADE_TOOL=portupgrade UPGRADE_PORT=gnome-applets-2.20.1 UPGRADE_PORT_VER=2.20.1 make WITH_FAM_SYSTEM=fam reinstall --- Restoring the old version ** Fix the installation problem and try again. [Updating the pkgdb in /var/db/pkg ... - 988 packages found (-0 +1) . done] ** Listing the failed packages (-:ignored / *:skipped / !:failed) ! x11/gnome-applets (gnome-applets-2.20.1) (install error) ** Could not clean up temporary directory: Directory not empty - /var/tmp/portupgradeOdM6jXk4 I'm seeing this on my AMD64 freebsd 6.3 system. Does anyone have ideas? Did you follow the /usr/ports/UPDATING? Cheers, Mezz Thanks Now I did and chek out the mess: ** Fix the problem and try again. ** Listing the failed packages (-:ignored / *:skipped / !:failed) - graphics/ImageMagick (marked as IGNORE) - java/diablo-jdk15 (marked as IGNORE) - japanese/lynx (marked as IGNORE) - java/jdk15 (marked as IGNORE) - textproc/p5-Text-ParseWords (port directory error) - x11-servers/xorg-printserver (marked as IGNORE) ! devel/ccrtp (ccrtp-1.5.2) (unknown build error) * devel/libzrtpcpp (libzrtpcpp-0.9.2) * net/twinkle (twinkle-1.0_4) * multimedia/libxine (libxine-1.1.7_3) ! x11/yelp (yelp-2.18.1_1) (linker error) * finance/gnucash-docs (gnucash-docs-2.2.0) * finance/gnucash (gnucash-2.2.0) ! security/seahorse (gnome-keyring-manager-2.20.0) (configure error) What is next? It doesn't show anything. You need to do it again to get actually error. The portupgrade has option to save build log or you can go to each port and do it by hand to get build error log. As for the seahorse part, are you sure you have complete ports tree up to date? The portupgrade is supposed to delete gnome-keyring-manager. If you still have it, remove it by manual and redo it. Cheers, Mezz -- [EMAIL PROTECTED] - [EMAIL PROTECTED] FreeBSD GNOME Team http://www.FreeBSD.org/gnome/ - [EMAIL PROTECTED] I've continued with the seahorse problem. In /usr/ports/UPDATING I couldn't find anything regarding seahorse! So I removed gnome-keyring-manager as you suggested. Then I did a portsnap fetch update. I then tried to install seahorse but got the following error: === epiphany-2.22.1.1 depends on shared library: ORBit-2.0 - found === epiphany-2.22.1.1 depends on shared library: pango-1.0.0 - found === Configuring for epiphany-2.22.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 how to create a ustar tar archive... gnutar checking whether to enable maintainer-specific portions of Makefiles... no checking build system type... amd64-portbld-freebsd6.3 checking host system type... amd64-portbld-freebsd6.3 checking for style of include used by gmake... GNU checking for gcc... cc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether cc accepts -g... yes checking for cc option to accept ISO C89... none needed checking dependency style of cc... gcc3 checking for a sed that does not truncate output... /usr/bin/sed checking for grep that handles long lines and -e... /usr/bin/grep checking for egrep... /usr/bin/grep -E checking for ld used by cc... /usr/bin/ld checking if the linker (/usr/bin/ld) is GNU ld... yes checking for /usr/bin/ld option to reload object files... -r checking for BSD-compatible nm... /usr/bin/nm -B checking whether ln -s works... yes
Re: port seahorse won't upgrade properly
On Mon, 14 Apr 2008 13:36:18 -0500, Dino Vliet [EMAIL PROTECTED] wrote: I've continued with the seahorse problem. In /usr/ports/UPDATING I couldn't find anything regarding seahorse! The gnome-keyring-manager is in /usr/ports/MOVED for gnome-keyring-manager - seahorse. For some reason, your portupgrade doesn't remove and replace to seahorse by itself. I don't know what happened. So I removed gnome-keyring-manager as you suggested. Then I did a portsnap fetch update. I then tried to install seahorse but got the following error: === epiphany-2.22.1.1 depends on shared library: ORBit-2.0 - found === epiphany-2.22.1.1 depends on shared library: pango-1.0.0 - found === Configuring for epiphany-2.22.1.1 snip checking what language compliance flags to pass to the C++ compiler... checking for DEPENDENCIES... configure: error: Package requirements ( glib-2.0 = 2.16.0 gmodule-2.0 gio-unix-2.0 = 2.16.0 gtk+-2.0 = 2.12.0 gtk+-unix-print-2.0 = 2.12.0 libxml-2.0 = 2.6.12 libxslt = 1.1.7 libgnome-2.0 = 2.14.0 libgnomeui-2.0 = 2.14.0 libglade-2.0 = 2.3.1 gconf-2.0 gnome-desktop-2.0 = 2.9.91 libstartup-notification-1.0 = 0.5 libnotify = 0.4 ) were not met: Package gnome-keyring-1 was not found in the pkg-config search path. Perhaps you should add the directory containing `gnome-keyring-1.pc' to the PKG_CONFIG_PATH environment variable Package 'gnome-keyring-1', required by 'libgnomeui', not found snip What now? I really don't have a clue. Hope you can help me out, Let me guess, you have selected to disable KEYRING option? It looks like this part is our fault. In Seahorse 2.22, it no longer provide option, which it required to have gnome-keyring dependency. I will fix it when I get back this afternoon by remove KEYRING option and depend on gnome-keyring. Meaning time, you can re-enable KEYRING and it should install Seahorse. Cheers, Mezz brgds Dino -- [EMAIL PROTECTED] - [EMAIL PROTECTED] FreeBSD GNOME Team http://www.FreeBSD.org/gnome/ - [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
