ldconfig -R issue (Was: Problems with icu - 3.8)

John Baldwin jhb at freebsd.org
Wed Feb 27 22:07:42 UTC 2008


On Monday 18 February 2008 05:10:24 am Sergey Matveychuk wrote:
> +stable@
> 
> Yoshihiro Ota wrote:
> > Why are so many people are bitten by this?  Is that the jobs of 
port-upgrading
> > tool to safe copy these libraries to compat so that all programs using
> > the old libraries works?
> 
> Portupgrade preserves the libraries in /usr/local/lib/compat/pkg:
> % ls /usr/local/lib/compat/pkg/
> libicudata.so.36.0      libicule.so.36.0        libicuuc.so.36.0
> libicui18n.so.36.0      libiculx.so.36.0
> libicuio.so.36.0        libicutu.so.36.0
> 
> ldconfig knows about the directory:
> % ldconfig -r | head -2
> /var/run/ld-elf.so.hints:
>          search directories: 
> /lib:/usr/lib:/usr/lib/compat:/usr/X11R6/lib:/usr/local/lib:/usr/local/lib/mysql:/usr/local/lib/compat/pkg
> 
> But ldconfig -R don't rescan them:
> % ldconfig -R
> % ldconfig -r | grep libicudata
>          231:-licudata.38 => /usr/X11R6/lib/libicudata.so.38
>          386:-licudata.38 => /usr/local/lib/libicudata.so.38
> 
> Could anybody investigate it? I have no time now.

Drop the .0 from the filenames or add libfoo.so.36 symlinks.

-- 
John Baldwin


More information about the freebsd-ports mailing list