This is definitely a gcc/egcs problem. There was many reports of this occuring a while back on the gnome lists (I think it was when red hat made egcs the default compiler). It only occurs if you use dynamic libraries compiled with egcs with programs compiled with gcc. To work around these problems, glibc-2.1 includes those functions, so that these problems do not occur. It is probably easiest to recompile gtk on your own machine, or find some binaries built with normal gcc. James. -- Email: [EMAIL PROTECTED] WWW: http://www.daa.com.au/~james/ On Thu, 19 Aug 1999 [EMAIL PROTECTED] wrote: > Matt Wilson discourseth: > > On Wed, Aug 18, 1999 at 06:18:55PM -0700, [EMAIL PROTECTED] wrote: > > > > ImportError: /usr/local/lib/libgtk-1.2.so.0: undefined symbol: > > > > __deregister_frame_info > > > > Perhaps libgtk-1.2.so.0 was built using a different glibc than > > the system on which this pygtk application is running? > > It's *something* like that, but I fear it's far more subtle since > __deregister_frame_info is neither defined nor referenced in libc. > *sigh*..libc problems are bad enough. :| > > Eric > To unsubscribe: echo "unsubscribe" | mail [EMAIL PROTECTED] > To unsubscribe: echo "unsubscribe" | mail [EMAIL PROTECTED]
