What happened after gnome upgrade??

[Kent Stewart]

On Wednesday 14 April 2004 09:21 pm, R. M. Los wrote:
> OK...so I got this idea, maybe if I did a "portupgrade
> gnomesystemmonitor", something would give....boy was I wrong.  What
> the heck is this?!
>
>
> <ERROR from 'portupgrade gnomesystemmonitor'>
> checking what warning flags to pass to the C compiler... -Wall
> -Wmissing-prototypes
> checking what language compliance flags to pass to the C compiler...
> checking for pkg-config... /usr/local/bin/pkg-config
> checking for libgnome-2.0 >= 2.0.0 libgnomeui-2.0 >= 2.0.0 gconf-2.0
> >= 1.1.5 libgtop-2.0 >= 2.5.2 libwnck-1.0 >= 2.5.0 gtk+-2.0 >=
> 2.3.0... Requested 'libgtop-2.0 >= 2.5.2' but version of libgtop is
> 2.0.7

I would suspect that you had ports that depend on glib-2.4.0 get updated 
in a bad order. Gtk-2.4.0, for example, depends on atk and pago, which 
also depend on glib-2.4.0. Portversion lists the ports in alphabetical 
order and not the order they need to be updated in. I have used -rR and 
seen things build out of order. They could have been built more than 
once because all I saw was the resulting package and it was built after 
a port that had it as a dependancy.

If you remember what you updated, you could force build them again. If 
you don't, you might consider portupgrade -rf glib. This is a start it 
and go away solution because it will take a lot of computer time. I 
would also set "BATCH=yes" in /etc/make.con

Kent

>
> configure: error: Library requirements (libgnome-2.0 >= 2.0.0
> libgnomeui-2.0 >= 2.0.0 gconf-2.0 >= 1.1.5 libgtop-2.0 >= 2.5.2
> libwnck-1.0 >= 2.5.0 gtk+-2.0 >= 2.3.0) not met; consider adjusting
> the PKG_CONFIG_PATH environment variable if your libraries are in a
> nonstandard prefix so pkg-config can find them.
> ===>  Script "configure" failed unexpectedly.
> Please report the problem to gnome at FreeBSD.org [maintainer] and
> attach the
> "/usr/ports/sysutils/gnomesystemmonitor/work/gnome-system-monitor-2.6
>.0/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/sysutils/gnomesystemmonitor.
> ** Command failed [exit code 1]: /usr/bin/script -qa
> /tmp/portupgrade22439.0 make
> ** Fix the problem and try again.
> ** The following packages were not installed or upgraded (*:skipped /
> !:failed)
>         ! sysutils/gnomesystemmonitor (gnomesystemmonitor-2.4.0)
> (configure error)
>
> </ERROR>

-- 
Kent Stewart
Richland, WA

http://users.owt.com/kstewart/index.html