seamonkey upgrade => 2.9.1

[Volodymyr Kostyrko]

H wrote:
>>>>>> WFM right now. Can you post your options? Can you show what ldd `which
>>>>>> seamonkey` gives you?
>>>>>
>>>>> of course
>>>>>
>>>>> #which seamonkey
>>>>> /usr/local/bin/seamonkey
>>>>
>>>> I was wrong here, it actually executes
>>>> /usr/local/lib/seamonkey/seamonkey-bin. Can you post ldd on that one?
>>>>
>>>
>>> here it is
>>
>> And I'm wrong again, it's so easy to be so silly...
>>
>
> don't say that :)
>
> I hope this is what you want:
>
> # ldd /usr/local/lib/seamonkey/seamonkey-bin
> /usr/local/lib/seamonkey/seamonkey-bin:

...

>          libintl.so.9 =>  /usr/local/lib/libintl.so.9 (0x2b252000)

And this is your poison. Can be found by 'compat' substring:

>          libpcre.so.1 =>  /usr/local/lib/libpcre.so.1 (0x2b25b000)
>          libpcre.so.0 =>  /usr/local/lib/compat/pkg/libpcre.so.0 (0x2b2b3000)

This library is referred twice by seamonkey. I seems that some library 
or seamonkey itself depends on older libpcre while some other binary 
needs newer libpcre.

It's not possible to clearly say which package should be rocompiled on 
your system, but you can fix it yourself:

  1. Update your ports (just to be sure you have the current version).
  2. As you are using portupgrade issue full update with "portupgrade -a".
  3. Install sysutils/bsdadminscripts.
  4. Issue "portupgrade `pkg_libchk -qoc`".

pkg_libchk checks binary files for missing links and reports them. 
portupgrade will rebuild all packages with missing symbols and relink 
them with currently available libraries.

-- 
Sphinx of black quartz judge my vow.