Re: It worked. Then I upgraded. Now it won't work :-(
- From: Owen Taylor <otaylor redhat com>
- To: "Fox, Kevin M" <KMFox mail bhi-erc com>
- Cc: Ivan Bilenkey <bilenkey unforgettable com>, gnome-list gnome org
- Subject: Re: It worked. Then I upgraded. Now it won't work :-(
- Date: 10 Mar 1999 11:10:05 -0500
"Fox, Kevin M" <KMFox@mail.bhi-erc.com> writes:
> It looks like one of the newer rpms, I think gnome-core-1.0.1-2 is the
> problem. gnome-core-1.0.1-1 didn't have the problem.
>
> I upgraded to 2 and bam.... same problem. The rpm people need to look at
> this right away...
The __register_frame_info problems come from mixing libraries
compiled with egcs with executables compiled with gcc-2.7.
My best guess is as to what is going on:
The original set of RPM's that were put up on the FTP site
were compiled with gcc-2.7.
They were replaced with a completely new set compiled
with egcs. Many of the release numbers (-1, -2) didn't
change. A few did. (This newer set fixed a number of
packaging problems in the initial set).
If you just upgraded to the ones with newer release
numbers, you'll get a mixed set of gcc and egcs
packages.
So, my suggested procedure for fixing your system if you
see this problem is to grab the entire set of RPM's
on the FTP site currently, and do:
rpm --force -Uvh *
Which will cause everything to be replaced, whether RPM
thinks it needs it or not.
(Don't get into the habit of using --force ;-)
Let me know if that works,
Owen
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]