Can someone explain the logic to me why you need the i386 version of glibc-devel installed on a x86_64 system in order to rebuild gcc for the x86_64? https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=113893
Besides the man and info files which are duplicates of the ones in the x86_64 glibc-devel package, the i386 package only contains files in /usr/lib.
Yes, I am going to go and try to install it but I am sure bothered as to why.
An additional issue is that the i386 glibc-devel is not part of the FC1 x86_64 test1 distribution (only glibc for the i686). Shouldn't I be able to rebuild any package in a distribution given only the packages contained in the distribution?
Do I need the i386 version of glibc-devel to rebuild on the sparc? How about the IA64 Itanium?
On Tue, 2004-01-27 at 17:18 -0500, Gene C. wrote:
Can someone explain the logic to me why you need the i386 version of glibc-devel installed on a x86_64 system in order to rebuild gcc for the x86_64? https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=113893
[snip]
Yes, I am going to go and try to install it but I am sure bothered as to why.
It's required so that you can build a gcc that supports -m32 and thus compile 32bit apps.
Cheers,
Jeremy
On Tuesday 27 January 2004 18:23, Jeremy Katz wrote:
On Tue, 2004-01-27 at 17:18 -0500, Gene C. wrote:
Can someone explain the logic to me why you need the i386 version of glibc-devel installed on a x86_64 system in order to rebuild gcc for the x86_64? https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=113893
[snip]
Yes, I am going to go and try to install it but I am sure bothered as to why.
It's required so that you can build a gcc that supports -m32 and thus compile 32bit apps.
OK, I can understand that ... but what if you do not want -m32 support on your system ... whatever.
Anyway, what I really don't completely understand is how to install additional packages without screwing things up. OK, the rpm -ivh glibc-devel... did the right thing and installed and I am now building gcc.
I just completed building glibc 2.3.2-101.4 for the x86_64 and have downloaded the i386/i686 packages also. I plan to put these into a single (local) repository and then do an upgrade on the x86_64 system using up2date. Hopefully up2date will know how to do things "right".
But what if I wanted to do this "manually" with just rpm? How do I do this "safely" so that I do not wind up with a system with 64 bit applications and 32 bit libraries. Right now my x86_64 system is pure testing so if I screw it up it is not a big deal. But this will be an issue later. Whether it has been big iron mainframes or small microcomputer, I am more familiar (more comfortable) with single architecture systems. Yes, the IA32 systems have i686 and athlon packages but they are few and easily understood. If I do not do things "right", I could replace stuff in /usr/bin, etc/ with 32 bit versions.
Before I started porting nessus to the 64 bit environment, I tried to install the 32 bit version. I soon found that the requires 32 bit libraries and it was like pulling on a bowl of spaghetti with more and more 32 bit libraries required. It became easier to do the port (which has been successfully BTW).
Fedora Core is fairly lean and mean with respect to the 32 bit libraries it installs (compared to the two dvd system that SUSE has). So how do we install additional 32 bit libraries "safely"? And how do we then maintain it when i386/i686/x86_64 packages are updated?
Any guidance will be appreciated.