Date: Wed, 06 Jun 2012 14:48:51 +0300 From: Volodymyr Kostyrko <c.kworr@gmail.com> To: H <hm@hm.net.br> Cc: gecko@FreeBSD.org Subject: Re: seamonkey upgrade => 2.9.1 Message-ID: <4FCF43A3.3030603@gmail.com> In-Reply-To: <4FCF3A5F.80505@hm.net.br> References: <4FCE7044.5060308@hm.net.br> <4FCF082B.2050904@gmail.com> <4FCF198C.1040703@hm.net.br> <4FCF1C7C.2020708@gmail.com> <51da39fbe03c8f0c30b0fe9846eb0169.squirrel@wm.matik.com.br> <4FCF2394.2020303@gmail.com> <353659e8a9859572fac4ea556a76ecb5.squirrel@wm.matik.com.br> <4FCF2982.5070107@gmail.com> <4FCF3A5F.80505@hm.net.br>
next in thread | previous in thread | raw e-mail | index | archive | help
H wrote: >>> /usr/local/lib/seamonkey/seamonkey-bin: >> # ldd /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: >> > > > Volodymyr > > can you tell what regex fucntion library has to do with the right mouse > button click? > > I have only pcre installed and it is up-to-date, as all other ports are > > seamonkey seems to require libpcre.so.0, it does not start without, this > is the older lib, libpcre.so.1 is coming from pcre which i just forced > an upgrade but no success > > even if this is the problem, why thunderbird is working fine, which is > using the exact same libs and was upgraded the same time? Maybe it fail only when it touches required functionality somewhere in gtk or cairo which in turn was compiled with older libpcre and there demands other calling conventions? You can take another route. 1. Force seamonkey to freeze. 2. Obtain core dump with gcore (1). 3. Open core dump with "gdb /usr/local/lib/seamonkey/seamonkey-bin seamonkey-bin.core". 4. Take backtrace with "bt full". However it would not provide clearly useful information unless all binaries wouldn't be stripped. To install unstripped binaries you should rebuild seamonkey and everything it depends on WITH_DEBUG and this will take much more time then fixing linkage the way I explained before. Try posting backtrace anyway. Maybe this clears things a bit. -- Sphinx of black quartz judge my vow.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4FCF43A3.3030603>