On Mon, Jun 07, 2004 at 03:30:09PM -0400, Robert Krueger wrote:
> Carol Spears wrote:
> >On Mon, Jun 07, 2004 at 02:53:44PM -0400, Robert Krueger wrote:
> >>"pkg-config --modversion glib-2.0' returned 2.2.3 but GLIB ( 2.3.6 )
> >>was found!"
> >i had similar problems with debian. i did not type "pkg-config
> >--modversion glib-2.0' but figured it out some other way (i read spew
> >too much).
> >the way i solved it on debian was to build a cvs version of glib in
> >/usr/local and add it to the path when i built my own deb of gtk2.
> >the developers lied to me or have something else going on when they told
> >me that debian gave them a working version.
> >too much script-fu in their background, i think.
> I have the feeling that if I just eliminate the files for glib 2.3.6 or
> the text that pkg-config found, that it would "configure" without
> complaint. I don't know how to find and eliminate this text or files,
well, that is the thing about linux. you are still trying to work with
the distribution. distributions break.
glib doesn't really do that much. or glib does a lot but very simply.
it is the bottom package. it is actually nothing but a gnu wrapper
around libc. so the changes there are not really important. unless
something really big happened to libc. libc has worked well forever. i
used it with the algol wrapper so long ago.
take advantage of the linux origins of the software. building your own
glib is very easy. it does not even need a lot of disc space.
i can make no promises that suse has provided a means to build a gtk2
easily, debian did for me. building my gtk2 deb needed to only see the
configuration file that my personal build of glib put there and
thankfully the rest just took build time. now my job is to keep them
from installing their broken deb again until they fix it.
are you absolutely married to suse for a distribution?
Gimp-user mailing list