Date: Tue, 15 Apr 2008 17:15:46 -0500 From: "Jeremy Messenger" <mezz7@cox.net> To: "Dino Vliet" <dino_vliet@yahoo.com> Cc: gnome@freebsd.org, freebsd-questions@freebsd.org Subject: Re: port seahorse won't upgrade properly Message-ID: <op.t9oasks49aq2h7@mezz.mezzweb.com> In-Reply-To: <846933.4958.qm@web51105.mail.re2.yahoo.com> References: <846933.4958.qm@web51105.mail.re2.yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 15 Apr 2008 17:04:00 -0500, Dino Vliet <dino_vliet@yahoo.com> = 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 >=3D 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 file= s > 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. > =3D=3D=3D> Script "configure" failed unexpectedly. > Please run the gnomelogalyzer, available from > "http://www.freebsd.org/gnome/gnomelogalyzer.sh", which will diagnose = the > problem and suggest a solution. If - and only if - the gnomelogalyzer = = > cannot > solve the problem, report the build failure to the FreeBSD GNOME team = at > gnome@FreeBSD.org, and attach (a) > "/usr/ports/www/epiphany/work/epiphany-2.22.1.1/config.log", (b) the = > output > of the failed make command, and (c) the gnomelogalyzer output. Also, i= t = > might > be a good idea to provide an overview of all packages installed on you= r = > 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 li= st > (gnome@FreeBSD.org), because attachments sent to FreeBSD mailing lists= = > are > usually discarded by the mailing list software. > *** Error code 1 > Stop in /usr/ports/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= = gecko (firefox) stuff. Maybe you have old nspr/nss/firefox leftover that= = wasn't remove, you tweak stuff or something else. Cheers, Mezz > Brgds > Dino -- = mezz7@cox.net - mezz@FreeBSD.org FreeBSD GNOME Team http://www.FreeBSD.org/gnome/ - gnome@FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?op.t9oasks49aq2h7>