On 07/12/11 16:54, Amit Kulkarni wrote:
OpenBSD 4.2 x11/gnome/gail includes libgailutil.so.18.1, this should have
been replaced by libgailutil.so.20.0 at OpenBSD 4.4, and the OpenBSD 4.4 ->
4.5 update was when gail was removed and gail became part of x11/gtk+2 with
libgailutil.so.22.0 included. Your issue is with old versions of packages
from 4.2 being left in current.
This could mean you had a package .libs-gale-xxxx or partial-gale-xxxx left
behind from an update. So there was always a libgailutil.so.18.1 version
present from 3-4yrs ago in /usr/local/lib.
To avoid problems use pkg_delete /var/db/pkg/.libs*, if there are no
dependencies the packages will be removed, if not your missing an update, or
maybe have a package that has since been removed. You should also remove
failed pkg_add's which create packages called partial-xxxxxxxxxx.
There are a number of others way to get an unclean system.
The current libgailutil is at version 26.0. You shouldn't have changed the
Makefile, or PLIST's. If you look back your see all the various bumps from
18.1 up to 26.0 for libgailutil in cvs. You should remove your gtk+2 and
start again with the correct version from cvs, if you truly cleaned your
system there is just no point in making those changes, gtk+2 should have
built without modification.
Hi all,
I built userland and still problems. I ultimately had to follow
Steve's suggestion and had to fetch the entire ports tree, and gtk+2
went though without any problems.
rm -rf /usr/ports/*
cvs co
I really don't understand why this came up. My infrastrucutre
directory which contains libtool is the same, only chnages I had was
the ports Makefile/distinfo's for ports like aterm, roxterm, junit,
rpm, amaya, postgresql-odbc/jdbc, etc... The ports which I have been
working on or fiddling. Nothing earth shattering and nothing really
important to the build, except maybe libgif.
Nigel,
I joined OpenBSD after 4.7, so I don't have the old utils lying
around. I did check around in cvs before asking you guys.
Thanks for your help guys!
amit
I have seen this twice now in 4 months, where getting a new tree
was the solution. Next time this happens I'm going to put the
suspect one away, and then compare it with the new (hopefully)
good one.
If others who've crashed into CVS problems can shed light on
why this happens, I'd be all ears.......
--STeve Andre'
