I had probs too.

Finally I took the source tarball configure/make/make installed that.

Then did the same for Winamp (which is why I was upgrading) and it all
worked.


----- Original Message -----
From: Tom Berger <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, April 20, 1999 11:42 PM
Subject: [expert] anyone else having problems with gtk/glib-update?


> Hi!
> Boy, what a mess...
> I installed/upgraded gtk 1.2.0 and glib 1.2.0. The gtk-packages
> (libs+devel) were vanilla Redhat rpms, glib had to be compiled because the
> RH lib-rpm is linked against some strange glibc version (pre-dependent
> libraries have a CC2 tag *shrug*, devel installed fine, though).
> Trouble is I don't get *anything* compiled which is linked against gtk
> 1.2.0.
> 1st: news peruser. The configure script failed to do a
> test compile. config.log said:
>
> > /usr/lib/libgtk.so: undefined reference to `__deregister_frame_info'
> > /usr/lib/libgtk.so: undefined reference to `__register_frame_info'
> > configure: failed program was:
> > #line 1309 "configure"
> > #include "confdefs.h"
>
> The author of News peruser had this to say:
>
> > These symbols are from libstdc++.so, not libgtk. That's about all I can
> > tell you.  What version of gcc and libc are you running? Have you
> > fiddled with them lately without doing an ldconfig?
>
> I am using the libstdc packages from the Manrake CD, ld.so.conf covers
> their directories...
> 'make' spat *dozens* of undefined references at me.
>
> 2nd: gentoo (a file manager). 'make' stutters:
>
> > In file included from /usr/include/glib.h:66,
> >                  from /usr/include/gdk/gdktypes.h:33,
> >                  from /usr/include/gdk/gdk.h:31,
> >                  from /usr/include/gtk/gtk.h:31,
> >                  from ../gentoo.h:43,
> >                  from ../cmd_rescan.c:6:
> > /usr/lib/glib/include/glibconfig.h:43: warning: ANSI C does not support
> > `long long'
> > /usr/lib/glib/include/glibconfig.h:44: warning: ANSI C does not support
> > `long long'
> [ad infinitum]
>
> Hm, this looks indeed like a glibc problem but *what* problem? I mean
> these files are standard Redhat, so why I am the only one who seems to
> get these errors?
> Last chance would be compiling gtk by myself, too. Duh... Is there anyone
> in here who got *all* the rpms installed (gtk/gtk-devel, glib/glib-devel)
> and has since then successfully compiled a source against them? If so,
> would you please tell me as exactly as possible which versions you did
> use?
>
> Thanks a lot
>
> tom
>
>   --
> "Whoever has any authority over you, no matter how small, will attempt to
use
> it." (Quigley's Law)
>  Thomas 'Tom' Berger, [EMAIL PROTECTED] No UCE. No spam. 'nuff said.
> *a.o.l.m.-FAQ*:  http://www.crosswinds.net/helsinki/~tombe/faq.html
>

Reply via email to