Re: : undefined symbol: __register_frame_info
- From: Ronald de Man <deman win tue nl>
- To: torben net Hawaii Edu, gnome-list gnome org
- Subject: Re: : undefined symbol: __register_frame_info
- Date: Thu, 11 Mar 1999 01:06:33 +0100
On Thu, Mar 11, 1999 at 06:21:32AM -1000, Torben Noerup Nielsen wrote:
> James,
>
> > -----Original Message-----
> > From: James Henstridge [mailto:james@daa.com.au]
> > Sent: Wednesday, March 10, 1999 4:40 AM
> > To: Jeff Miller
> > Cc: Gnome List; gisli@master.adams.com
> > Subject: Re: : undefined symbol: __register_frame_info
> >
> >
> > As someone mentioned earlier, this problem is most likely caused by
> > running a program compiled with a newer egcs with a copy of glibc (most
> > likely 2.0.x) compiled with gcc. The two options are to recompile the
> > applications on your own machine with your normal compiler, or to upgrade
> > to glibc 2.1, which contains a fix for this problem (it is backward
> > compatible, so you shouldn't have too many troubles).
>
> I would like to upgrade to glibc 2.1, but it isn't available as far as I can
> tell. When might this all be resolved? Also, if someone makes it available
> as an RPM, there really is no ``unsafe" fiddling with system libraries. Not
> that I would be bothered if I had to do that.
>
> Thanks, Torben
>
>
It has been available ever since it got out. glibc-2.1 only got retracted
from the official GNU mirrors for the (IMHO) silly reason that the
README advised against using gcc-2.8. You can find glibc-2.1 for
example at ftp.funet.fi in /pub/gnu/funet.
Ronald
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]