PDA

View Full Version : [SOLVED] i686 packages on a 64-bit install



milomak
26th March 2011, 07:47 PM
was running an upgrade and it struck me how many i686 packages were being installed/upgraded.

is this something to be lived with, or is there a way to limit the i686 packages?

smr54
26th March 2011, 07:49 PM
Generally, if they're installed, they're needed. There are some programs that will only run in 32 bit mode--skype, for example. If you've installed Skype, then you have a bunch of i686 programs that had to be installed for it to work.

stevea
26th March 2011, 08:35 PM
Actually there are VERY FEW packages in the Fedora Repo that require 32bit. I checked this back around F12 and it was someassembler tool (maybe 'nasm') and one other.

So the main reason you are getting a load of 32bit packages is to allow ou rto run 3rd party 32bit packages.

Remove then with 'yum erase' and check what is removed for dependencies - I'll wager it's not much.

---------- Post added at 03:35 PM ---------- Previous post was at 03:21 PM ----------

I just did a
yum erase \*.i386
yum erase \*.i686

The only 64bit package that was removed for dependency was wine.


Oddly wine has a load of 32bit dependencies ...

$ yum install wine
...
Dependencies Resolved
...
Installing:
wine x86_64 1.3.14-2.fc14 updates 32 k
Installing for dependencies:
alsa-lib i686 1.0.24-1.fc14 updates 382 k
cairo i686 1.10.2-1.fc14 updates 458 k
cdparanoia-libs i686 10.2-9.fc13 fedora 46 k
cyrus-sasl-lib i686 2.1.23-12.fc14 fedora 135 k
db4 i686 4.8.30-2.fc14 fedora 620 k
dbus-libs i686 1:1.4.0-2.fc14 updates 136 k
expat i686 2.0.1-10.fc13 fedora 78 k
flac i686 1.2.1-6.fc12 fedora 239 k
fontconfig i686 2.8.0-2.fc14 fedora 186 k
freetype i686 2.4.2-4.fc14 updates 350 k
.....
...
Install 88 Package(s)
Upgrade 18 Package(s)

Total download size: 62 M

jvillain
26th March 2011, 09:27 PM
Thanks for the tip on \*i386 when I originally blew out all mine I did it via

rpm -qa |grep i386

etc, then took them out a few at a time. Mind you removing 32bit glibc first goes a long ways towards identifying the 32 bit packages. Your way is much more elegant. I agree for the most part if you still have 32 bit packages installed they are probably left over from the dark days or some thing proprietary. 32bit wine packages aren't a surprise as even 64 bit windows is mostly 32bit still.

bluestealth
31st March 2011, 09:57 PM
Oddly wine has a load of 32bit dependencies ...

Not so much, windows applications are still predominantly 32-bit, it would be almost useless to install only 64-bit libraries instead of multilib.
If you desired you could build Wine64 only and install that, but it probably wouldn't be very useful, just as windows x64 without WOW64 is useless.
Sadly the only people to rage against here are window developers who still do not make 64 bit applications, since largely there is no need. If you like focus your anger at Adobe, who we know is at fault for flash. ;)

jvillain
1st April 2011, 09:56 PM
Well lets be fair. You can only be mad at Adobe every other week because one week they have support for 64 bit Linux then the next week they don't. Then they do and then they don't.