Re: : undefined symbol: __register_frame_info (The solution!)
- From: Gisli Ottarsson <gisli master adams com>
- To: gnome-list gnome org
- Subject: Re: : undefined symbol: __register_frame_info (The solution!)
- Date: 11 Mar 1999 13:14:27 -0500
Let me restate the problem:
I upgraded (rpm -U) to 1.0 from 0.99.8 only to find that some
applications stopped working, most notably Electric Eyes (ee). When
run, these applications would fail with the message:
undefined symbol: __register_frame_info
A subsequent upgrade to an enhanced 1.0 (available on mirrors on
Tuesday night and dated Mar 6th-7th) made this problem worse rather
than better. Additional applications started failing in the same way.
My understanding of the problem is as follows:
There are duplicate RPMs out there, identically versioned, based on
the same source code, but one compiled with EGCS while the other is
compiled with GCC. The missing symbol is supposedly related to a
version of glibc which supersedes the one on my machine. These RPMs
cannot, apparently, be mixed.
The solution:
Grab a *complete* distribution, regardless of RPM telling you that you
already have pieces of it installed. Then, when upgrading, force
installation of the new, identically named, RPM by typing:
rpm -U --force *.rpm
This will force the upgrade of the all the packages, also those that
RPM thinks it already has installed.
This solved my problem, although I did have problems with
libgnome.so.2 but this is unrelated and should be the topic of another
post.
Caveat:
Use --force with caution. I would recommend running the upgrade first
without the --force option to verify that RPM is only warning that
packages are already installed. This is the only thing you want to be
forcing.
Thanks to all that shed light on this.
Gisli
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]