Hi, I'm preparing a new x86_64 build machine and I'm looking at installed rpms. I have found a lot of packages are marked i386 or i686. I have even found I have two version of package installed: glibc-2.3.4-2.36-i686 glibc-2.3.4-2.36-x86_64
What's the reason in duplicity and why not all packages are x86_64. Thanks in advance, David
On Tue, Jul 31, 2007 at 02:38:42PM +0200, David Hrbá? enlightened us:
I'm preparing a new x86_64 build machine and I'm looking at installed rpms. I have found a lot of packages are marked i386 or i686. I have even found I have two version of package installed: glibc-2.3.4-2.36-i686 glibc-2.3.4-2.36-x86_64
What's the reason in duplicity and why not all packages are x86_64. Thanks in advance, David
Some programs are not available in 64-bit packages (e.g. openoffice). Those packages need 32-bit libraries to run, so you are seeing the necessary packages for those 32-bit apps.
Matt
On 7/31/07, David Hrbác( hrbac.conf@seznam.cz wrote:
Thank you, that did not come to my mind.
Keep in mind that some of the i386/i686 packages may interfere with x86_64 builds. Multi-arch gets very interesting when you're building software. You may have to remove some/all of them, or be very specific about the build instructions you issue. It's possible to end up with an x86_64 package linked to i686 junk if you're not careful.
-
David Hrbác( -
David Hrbáč
-
Jim Perrin -
Matt Hyclak