gcc installation problems

Mario Morrell

unread,

Dec 31, 2009, 6:42:57 PM12/31/09

to

Hi,
Thanks group for your help in advance.

I am running Fedora 12 on an i686 machine and I am attempting to install
gcc-4.4.2-20.fc12.i686 either with the Add/Remove Software program or
yum so that I can compile some programs from source. I end up getting
the error message:
glibc=2.11-2 needed by glibc-devel-2.11-2.i686
glibc=2.11-2 needed by glibc-headers-2.11-2.i686
Currently I have glibc-2.11-4.i686 installed and
libgcc-4.4.2-20.fc12.i686 installed.
Obviously I'm missing something here and would appreciate your help.

Mario

Wanna-Be Sys Admin

unread,

Dec 31, 2009, 8:18:11 PM12/31/09

to

Mario Morrell wrote:

Did you try cleaning the yum headers, metadata and cache? Or even a yum
clean all? This is a common package that is ignored when you have
things out of sync. It could be another issue, but you'll need to post
the full output (or all of the relevant portions of it), as sometimes
you need to remove a dummy RPM or the like.
--
Not really a wanna-be, but I don't know everything.

Mario Morrell

unread,

Dec 31, 2009, 10:48:55 PM12/31/09

to

I ran yum clean all with the results of:
Cleaning up everything
0 delta-package files removed
I again tried to install gcc, and get the same message.

Michal Jaegermann

unread,

Jan 2, 2010, 1:28:06 AM1/2/10

to

Mario Morrell <morrellm...@qwest.net> wrote:
>
> I am running Fedora 12 on an i686 machine and I am attempting to install
> gcc-4.4.2-20.fc12.i686 either with the Add/Remove Software program or
> yum so that I can compile some programs from source. I end up getting
> the error message:
> glibc=2.11-2 needed by glibc-devel-2.11-2.i686
> glibc=2.11-2 needed by glibc-headers-2.11-2.i686

The only glibc requirement for gcc-4.4.2-20.fc12 is
glibc-devel >= 2.2.90-12 and this in turn would need _the same_ version
of glibc.

> Currently I have glibc-2.11-4.i686 installed and

Then you do not running Fedora 12, where the current release version
of glibc is glibc-2.11-2 but, judging from your error messages, some
kind of a mess where glibc and its "sub-packages" are of different
versions and it is hard to guess how did you get into that sorry state.
Probably using rpm with '--nodeps' and/or '--force'. If you do such
things it is up to you to extricate yourself from a self created swamp.
Such changes should be done in _one_ consistent transaction. Nothing
to do at all with gcc.

Most likely you should

yum downgrade glibc-2.11-2.i686

and check results with

rpm -qa 'glibc*'

Once you will see the same version in answers then you can install other
things. 'rpm --verify -a' checks sanity of all rpm packages you
installed. Redirect an output to a file as it may be a long one and
this will take a while. See 'man rpm' for meanings of markers for
'--verify' (in a section called, surprise, 'VERIFY OPTIONS').

Michal

Nico Kadel-Garcia

unread,

Jan 2, 2010, 11:32:24 PM1/2/10

to

On Jan 2, 1:28 am, Michal Jaegermann <mic...@gortel.phys.ualberta.ca>
wrote:

Ouch. It's also possible that our here has something else going on,
like pointers to a separate repository that is non-Fedora repository
marked as a 'preferred' repository, or a partially failed insallation
of glibc dangling around so he has an older and a current glibc
package in place (which I've seen!)

Running "rpm -qa | grep glibc" would be indicative.

Mario Morrell

unread,

Jan 4, 2010, 1:02:01 PM1/4/10

to

I made sure that yum is only using a Fedora repository and running "
rpm -qa | greb glibc" gives me:
glibc-2.11-4.i686
glibc-common-2.11.4.i686

When I try to downgrade to glibc-2.11-2.i686 yum comes back and tells me
there is no glibc-2.11-2.i686 available.