Date: Thu, 07 Jun 2012 13:42:10 +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: <4FD08582.4070602@gmail.com> In-Reply-To: <4FD0827C.9050404@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> <4FCF43A3.3030603@gmail.com> <4FCF4876.8090705@hm.net.br> <4FCF4E30.8040305@gmail.com> <4FD0827C.9050404@hm.net.br>
next in thread | previous in thread | raw e-mail | index | archive | help
H wrote: > > well, pkg_libchk found some inconsistencies and after solving that > nothing changed > > I found a package 2.9.1 and it behaves the same erroneous way > > I went back to 2.9 and everything runs fine again > > so seems there is nothing wrong on my machine but the seamonkey port is > fucked up somehow as well as Firefox 12 Just to be sure, what does pkg_libchk report now and what ldd -a whos on your seamonkey binary? -- Sphinx of black quartz judge my vow.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4FD08582.4070602>