On 16.10.2005 17:52, Patrys :: Patryk Zawadzki wrote:
> Could you do the same with the --enable-optimization line removed? I
> think this might be the problem and having this removes is still better
> than using Mozilla-provided binary packages (and they happen to have
> this option removed when c
Dnia 16-10-2005, nie o godzinie 10:27 +0200, Jan Palus napisał(a):
> On 16.10.2005 02:08, Patrys :: Patryk Zawadzki wrote:
> > Yes, i686 for that case.
> >
> > After upgrading I end up with:
> >
> > [EMAIL PROTECTED] ~]$ mozilla-firefox
> > /usr/lib/mozilla-firefox/firefox-bin: symbol lookup
> >
Dnia 16-10-2005, nie o godzinie 10:44 +0200, Fryderyk Dziarmagowski
napisał(a):
> it's because you added --disable-xft. it should be always enabled since
> pango/gtk+ uses xft for font rendering.
Actually not. It uses it internally. Mozilla developer docs explicitly
say to always use --disable-xft
Is it possible to fix it in this year!?
On Sat, Oct 15, 2005 at 12:09:33 +0200, Tomasz Pala wrote:
> athlon and amd64 are ok, while i686:
>
> Retrieving ac::packages.ndir.md...
> Retrieving ac::packages.ndir.gz...
> .. 100.0% [9.2M (363.2K/s)]
>
--- "Patrys :: Patryk Zawadzki" <[EMAIL PROTECTED]> wrote:
> > > Could someone test if after my changes Firefox still suffers from memory
> > > corruption
> >
> > It's currently being built to i386 ac-test. Go ahead and check if it
> > works better in your test case (you're using ix86, right?).
On 16.10.2005 02:08, Patrys :: Patryk Zawadzki wrote:
> Yes, i686 for that case.
>
> After upgrading I end up with:
>
> [EMAIL PROTECTED] ~]$ mozilla-firefox
> /usr/lib/mozilla-firefox/firefox-bin: symbol lookup
> error: /usr/lib/mozilla-firefox/components/libgfx_gtk.so: undefined
> symbol: pang
