gcc installation problems
in [Setup]
|
From: Mario Morrell on 31 Dec 2009 18:42 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
From: Wanna-Be Sys Admin on 31 Dec 2009 20:18 Mario Morrell wrote: > 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 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.
From: Mario Morrell on 31 Dec 2009 22:48 On Thu, 2009-12-31 at 17:18 -0800, Wanna-Be Sys Admin wrote: > Mario Morrell wrote: > > > 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 > > 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. 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.
From: Michal Jaegermann on 2 Jan 2010 01:28 Mario Morrell <morrellmariocind(a)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
From: Nico Kadel-Garcia on 2 Jan 2010 23:32
On Jan 2, 1:28 am, Michal Jaegermann <mic...(a)gortel.phys.ualberta.ca> wrote: > Mario Morrell <morrellmarioc...(a)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'). 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. |