Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 8 Feb 2004 02:58:35 +0000
From:      Stacey Roberts <stacey@vickiandstacey.com>
To:        Stacey Roberts <stacey@vickiandstacey.com>
Cc:        freebsd-gnome@freebsd.org
Subject:    Re: portupgrade -rf gettext -m BATCH=yes fails at gnomemeeting stage
Message-ID:  <20040208025835.GC38997@crom.vickiandstacey.com>
In-Reply-To: <20040207232914.GB38997@crom.vickiandstacey.com>
References:  <200402072125.i17LPtsN020404@Demon.vickiandstacey.com> <opr20rk3rp8ckrg5@smtp.central.cox.net> <20040207232914.GB38997@crom.vickiandstacey.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Hello,

----- Original Message -----
From: "Stacey Roberts <stacey@vickiandstacey.com>"
To: To Jeremy Messenger
Date: Sat, 07 Feb, 2004 23:29 GMT
Subject: Re: portupgrade -rf gettext -m BATCH=yes fails at gnomemeeting stage

> Hello,
>       Thanks for the reply.
> 
> ----- Original Message -----
> From: "Jeremy Messenger <mezz7@cox.net>"
> To: To Stacey Roberts
> Date: Sat, 07 Feb, 2004 21:35 GMT
> Subject: Re: portupgrade -rf gettext -m BATCH=yes fails at gnomemeeting stage
> 
> > On Sat, 7 Feb 2004 21:25:55 GMT, Stacey Roberts 
> > <stacey@vickiandstacey.com> wrote:
> > 
> > >After fresh cvsup of a system that had *NOT* been upgraded / affected by 
> > >the gettext issue (that is still running gettext-1.12.x), running the 
> > >above command finally fails with the following tail of the upgrade 
> > >process:
> > 
> > <snip>
> > 
> > >--->  Skipping 'x11/gnome2' (gnome2-2.4.1) because 'net/gnomemeeting' 
> > >(gnomemeeting-0.98.5_1) failed
> > >** The following packages were not installed or upgraded (*:skipped / 
> > >!:failed)
> > >        ! net/gnomemeeting (gnomemeeting-0.98.5_1)      (configure error)
> > >        * x11/gnome2 (gnome2-2.4.1)
> > >#
> > 
> > It shows that it's only one failed. Can you try to do the 'portsclean -C' 
> > then try 'portupgrade -f gnomemeeting\*' to get the more info of your 
> > errors? In your message, it doesn't show any error details of gnomemeeting.
> > 

I managed to catch the error as the rebuild was progressing.., Here is the point at which the failure for gnomemeeting fails:

Using $(sysconfdir)/gconf/schemas/ as install directory for schema files
checking for pkg-config... /usr/local/bin/pkg-config
checking for gtk+-2.0 >= 2.0.6 esound >= 0.2.28 gconf-2.0 >= 1.2.1 libxml-2.0 >= 2.4.23 libgnome-2.0 >= 2.0.0 libgnomeui-2.0 >= 2.0.0... yes
checking GNOMEMEETING_CFLAGS... -DORBIT2=1 -D_THREAD_SAFE -I/usr/local/include/atk-1.0 -I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include -I/usr/local/include -I/usr/local/include/orbit-2.0 -I/usr/local/include/libxml2 -I/usr/local/include/libbonobo-2.0 -I/usr/local/include/bonobo-activation-2.0 -I/usr/local/include/libart-2.0 -I/usr/X11R6/include/gtk-2.0 -I/usr/X11R6/lib/gtk-2.0/include -I/usr/X11R6/include/pango-1.0 -I/usr/X11R6/include -I/usr/local/include/freetype2 -I/usr/X11R6/include/gconf/2 -I/usr/X11R6/include/libgnome-2.0 -I/usr/X11R6/include/gnome-vfs-2.0 -I/usr/X11R6/lib/gnome-vfs-2.0/include -I/usr/X11R6/include/libgnomeui-2.0 -I/usr/X11R6/include/libgnomecanvas-2.0 -I/usr/X11R6/include/libbonoboui-2.0
checking GNOMEMEETING_LIBS... -Wl,--export-dynamic -pthread -L/usr/local/lib -L/usr/X11R6/lib -lesd -laudiofile -lgnomeui-2 -lSM -lICE -lbonoboui-2 -lxml2 -lgnomecanvas-2 -lgnome-2 -lpopt -lart_lgpl_2 -lpangoft2-1.0 -lgtk-x11-2.0 -lgdk-x11-2.0 -lXrandr -lXi -lXinerama -latk-1.0 -lgdk_pixbuf-2.0 -lpangoxft-1.0 -lXft -lfreetype -lz -lXrender -lXext -lfontconfig -lpangox-1.0 -lX11 -lpango-1.0 -lbonobo-2 -lgconf-2 -lgnomevfs-2 -lbonobo-activation -lORBit-2 -lgobject-2.0 -lm -lgmodule-2.0 -lgthread-2.0 -lglib-2.0 -liconv
checking for long... yes
checking size of long... 4
checking whether OS type is supported... yes
checking for PTLib includes...
checking for /usr/ports/net/gnomemeeting/../../devel/pwlib/work/pwlib/include/ptlib/pprocess.h... no
configure: error: You need PTLib's header files to build GnomeMeeting
===>  Script "configure" failed unexpectedly.
Please report the problem to roger@FreeBSD.org [maintainer] and attach the
"/usr/ports/net/gnomemeeting/work/gnomemeeting-0.98.5/config.log" including
the output of the failure of your make command. Also, it might be a good idea
to provide an overview of all packages installed on your system (e.g. an `ls
/var/db/pkg`).
*** Error code 1
  
Stop in /usr/ports/net/gnomemeeting.
** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade25223.14 make
** Fix the problem and try again.

Needless to say, given the amount of problems this very-same-issue had during the bump from Gnome-2.2 to Gnome-2.4, I'd have thought I'd seen the last of this.., but here it is once more..,

I don't suppose you'd know how I might solve this?
(other than re-installing Gnome to "see if that will fix this") 


Regards,

Stacey

> 
> Err.., I think I might have made a boo-boo here.., I actually just tried to see if this "was one of those things" and actually re-issued the same command to see if it might work second time around.
> 
> Is it at all possible to kill this running "portupgrade -rf gettext -m BATCH=yes" command in mid-execution and do as you suggest?
> 
> Regards,
> 
> Stacey
> 
> > Cheers,
> > Mezz
> > 
> > 
> > -- 
> > bsdforums.org 's moderator, mezz.
> > 
> 
> -- 
> Stacey Roberts
> B. Sc (HONS) Computer Science
> 
> Web: www.vickiandstacey.com
> _______________________________________________
> freebsd-gnome@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-gnome
> To unsubscribe, send any mail to "freebsd-gnome-unsubscribe@freebsd.org"

-- 
Stacey Roberts
B. Sc (HONS) Computer Science

Web: www.vickiandstacey.com



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040208025835.GC38997>