Re: required glibc-common = 2.12-1.25.el6 vs installed glibc-common-2.12-1.25.el6_1.3.x86_64

seth vidal <[email protected]>
Newsgroups gmane.linux.rpm.yum
Message-ID <20111108161204.2b1c91aa@opus>
On Tue, 8 Nov 2011 14:55:51 -0600 (CST)
Connie Sieh <[email protected]> wrote:

> On Tue, 8 Nov 2011, seth vidal wrote:
> 
> > On Tue, 8 Nov 2011 14:41:32 -0500
> > "Terre Porter" <[email protected]> wrote:
> >
> >> I'm not sure if this is a yum issue or just me being a bit brain
> >> dead.
> >>
> >> I'm trying to install gcc on a Scientific Linux release 6.1
> >> (Carbon) box using yum but it keeps giving me the following error.
> >>
> >> Error: Package: glibc-2.12-1.25.el6.i686 (sl)
> >>            Requires: glibc-common = 2.12-1.25.el6
> >>            Installed: glibc-common-2.12-1.25.el6_1.3.x86_64
> >> (@sl-fastbugs/6) glibc-common = 2.12-1.25.el6_1.3
> >>            Available: glibc-common-2.12-1.25.el6.x86_64 (sl)
> >>                glibc-common = 2.12-1.25.el6
> >>
> >> Anyone else having this problem, or know of how to fix it?
> >>
> >
> > 1. it looks like you have a newer version of glibc than what gcc in
> > the sl 6.1 release has been built against
> > 2. you should probably ping the scientific linux folks to see if
> > this is a known repo issue
> >
> > -sv
> > _______________________________________________
> > Yum mailing list
> > [email protected]
> > http://lists.baseurl.org/mailman/listinfo/yum
> >
> 
> You need to enable the "fastbugs" repo as it seems you have installed
> the glibc from that repo .  The "fastbugs" repo has
> glibc-2.12-1.25.el6_1.3 and the "standard" repo has
> glibc-2.12-1.25.el6 .
> 
>     yum --enablerepo=fastbugs install gcc
> 
> This will enable the fastbugs repo which has the glibc versions that
> you have installed already.
> 

Connie,
 Thanks - I didn't feel like digging through the repos for the answer
 but I figured it was something like that.

thanks
-sv
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.