On Fri, 22 Mar 2002, Frederic Crozat wrote:
On Thu, Mar 21, 2002 at 07:47:55PM +0100, Frederic Crozat wrote:
Name: gtk+2.0 Relocations: (not
relocateable) Version : 2.0.0 Vendor:
MandrakeSoft Release : 1mdk Build Date:
Thu Mar 21 19:05:=
59 2002
=20
- Disabled linux-fb target temporarily, causing HUGE memory leak=20
(anyway, x11 and linux-fb target can't coexist for now.)
Oh no! Is this HUGE memory leak a known bug to the GTK+ developers?
Why can't x11 and linux-fb coexist? The library names are
non-conflicting. At least in the 1.3 releases, there was libgtk-x11 and
libgtk-linux-fb, and so on. It would be even nicer to have run-time
selection, but compile time is good enough for now.
Ask Abel, I just adapted his rpms..
They REALLY cann't coexist for now. Try compiling both x11 target and
linux-fb target seperately, and compare their gtk+-2.0.pc and gdk-2.0.pc.
For gtk+ 1.3.1x package, the x11 copy of gtk+-2.0.pc overwrites the one
from linux-fb target, that means any program linked against gtk+ would
be unconditionally linked against libX11 as well.
Abel
PS Actually, x11 is still the only 'blessed' target in gtk+ 2.0.0. You
can't even compile the linux-fb target from vanilla source.
--
GPG Key: (0xC67186FF) http://deaddog.org/gpg.asc
