Date: Wed, 18 Oct 2006 00:20:33 -0300 From: Duane Whitty <duane@dwlabs.ca> To: freebsd-ports@freebsd.org Subject: gconf2, missing libicui18n.so.34, icu, and portupgrade Message-ID: <20061018032033.GD20196@dwpc.dwlabs.ca>
next in thread | raw e-mail | index | archive | help
I just want to let everyone know upfront not to take this as a complaint. I litterally live for figuring this kind of stuff out :) I've been bitten a couple of times when try to run previously working apps and when trying to upgrade apps by the following message dwpc@ /home/duane>firefox /libexec/ld-elf.so.1: Shared object "libicui18n.so.34" not found, required by "gconfd-2" No problem there I figured, I just need to rebuild some ports. #portupgrade -rRv icu\* dwpc@ /usr/ports# portupgrade -rRv icu\* ---> Session started at: Tue, 17 Oct 2006 20:55:20 -0300 ** No need to upgrade 'icu-3.6' (>= icu-3.6). (specify -f to force) ---> ** Upgrade tasks 78: 0 done, 1 ignored, 0 skipped and 0 failed [snip] ---> Upgrade of multimedia/gstreamer-plugins80 started at: Tue, 17 Oct 2006 21:14:29 -0300 ---> Upgrading 'gstreamer-plugins80-0.8.12_3' to 'gstreamer-plugins80-0.8.12_2,1' (multimedia/ gstreamer-plugins80) [snip] /libexec/ld-elf.so.1: Shared object "libicui18n.so.34" not found, required by "gconftool-2" ---> Upgrade of www/mozilla started at: Tue, 17 Oct 2006 21:56:58 -0300^M ---> Upgrading 'mozilla-1.7.13,2' to 'mozilla-1.7.13_1,2' (www/mozilla)^M ---> Build of www/mozilla started at: Tue, 17 Oct 2006 21:56:58 -0300 [snip] install -o root -g wheel -m 444 /usr/ports/www/mozilla/work/mozilla.desktop /usr/local/share/ applications^M ===> Building Chrome's registry...^M /libexec/ld-elf.so.1: Shared object "libicui18n.so.34" not found, required by "gconfd-2"^M [Now I press ^T] load: 0.00 cmd: regchrome 26070 [kserel] 0.10u 0.02s 0% 11632k^M^M [Machine seems to have hung] [I press ^C] ^C** Command failed [exit code 2]: /usr/bin/script -qa /tmp/portupgrade.30582.3 env PORT_UPGRAD E=yes make reinstall^M I thought all of this was a bit strange because our developers don't usually just pull the rug out from I thought all of this was a bit strange because our developers don't usually just pull the (.so) rug out from under us without doing proper symlinking etc. Checking it out further, I find this: dwpc@ /usr/local/lib>ll lrwxr-xr-x 1 root wheel 18 Oct 15 18:24 libicui18n.so -> libicui18n.so.36.0 lrwxr-xr-x 1 root wheel 18 Oct 15 18:24 libicui18n.so.36 -> libicui18n.so.36.0 -r--r--r-- 1 root wheel 1474969 Oct 15 18:24 libicui18n.so.36.0 I never tell portupgrade to delete obsolete shared libraries so should not libicui18n.so.34 still be available? I managed to to gaim upgraded around this so I imagine I'll get everything else figured out as well. What I would really like though is to understand how the shared object library linking works and what, if anything, I should have done differently. I hope this helps someone else and thanks in advance. Most Respectfully, Duane Whitty
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20061018032033.GD20196>