pero profe, mi duda es, [root@localhost ~]#yum install libgcc.i686 --setopt=protected_multilib=false
o debo agregar esta linea en el archivo yum.conf ?? 2015-09-03 16:45 GMT-03:00 Enrique Herrera Noya < enrique.herreran...@gmail.com>: > En el punto 3 del mensaje > Te dice que uses .. > > yum install libgcc.i686 > --setopt=protected_multilib=false > > De esa forma se salta la verificación y te instala la libreria de 32 bit > > Si no entiendes el error aplica traductor > El 03-09-2015 15:27, "Luis Enrique Araneda" <leacb...@gmail.com> escribió: > > > Estimados un problemilla en el camino, como lo hago para forzar la > > instalación de un paquete en especifico, necesito instalar libgcc.i686 > en > > una maquina de 64 bit, para la aplicación que quiero correr necesito esta > > de 32, me arroja lo siguiente: > > > > Haber si el profe Enrique Herrera me apaña! > > > > [root@localhost ~]# yum install libgcc.i686 > > Loaded plugins: fastestmirror, refresh-packagekit, security > > Loading mirror speeds from cached hostfile > > * base: mirror.gtdinternet.com > > * epel: epel.gtdinternet.com > > * extras: mirror.gtdinternet.com > > * updates: mirror.ci.ifes.edu.br > > Setting up Install Process > > Resolving Dependencies > > --> Running transaction check > > ---> Package libgcc.i686 0:4.4.7-16.el6 will be installed > > --> Finished Dependency Resolution > > Error: Multilib version problems found. This often means that the root > > cause is something else and multilib version checking is just > > pointing out that there is a problem. Eg.: > > > > 1. You have an upgrade for libgcc which is missing some > > dependency that another package requires. Yum is trying to > > solve this by installing an older version of libgcc of the > > different architecture. If you exclude the bad architecture > > yum will tell you what the root cause is (which package > > requires what). You can try redoing the upgrade with > > --exclude libgcc.otherarch ... this should give you an error > > message showing the root cause of the problem. > > > > 2. You have multiple architectures of libgcc installed, but > > yum can only see an upgrade for one of those arcitectures. > > If you don't want/need both architectures anymore then you > > can remove the one with the missing update and everything > > will work. > > > > 3. You have duplicate versions of libgcc installed already. > > You can use "yum check" to get yum show these errors. > > > > ...you can also use --setopt=protected_multilib=false to remove > > this checking, however this is almost never the correct thing to > > do as something else is very likely to go wrong (often causing > > much more problems). > > > > Protected multilib versions: libgcc-4.4.7-16.el6.i686 != > > libgcc-4.4.7-4.e l6.x86_64 > > You could try using --skip-broken to work around the problem > > You could try running: rpm -Va --nofiles --nodigest > > > > > > -- > > > > *Luis Araneda Cortés* > > > -- *Luis Araneda Cortés*