Ugh. One of our internal servers crashed so bad I just went out and bought a new machine to replace it. The old server was Pentium-4 based and running CentOS-5. When I installed CentOS on the new machine, I used the 64-bit version, partly because that habit is almost automatic nowadays, and partly because the new machine has 6GB of RAM, so 32-bit seemed not very appropriate. Anyway, I've managed to configure every one of the old server's many functions to match on the new server but one: I need the 32-bit version of compat-gcc-34. (Or at least I need to be able to compile 32-bit binaries with the already available version.) I can't seem to do this; am I just missing something? In retrospect, installing the 64-bit OS may have been foolish. But it's too late now. I've spent several days installing/loading/configuring this system to the point it's at now. It would be a pity to have to start over completely just to enable this one (very critical) function. -Alan
On Tue, Mar 29, 2011 at 5:35 PM, Alan M. Evans <ame1 at extratech.com> wrote:> Ugh. > > One of our internal servers crashed so bad I just went out and bought a > new machine to replace it. > > The old server was Pentium-4 based and running CentOS-5. When I > installed CentOS on the new machine, I used the 64-bit version, partly > because that habit is almost automatic nowadays, and partly because the > new machine has 6GB of RAM, so 32-bit seemed not very appropriate. > > Anyway, I've managed to configure every one of the old server's many > functions to match on the new server but one: I need the 32-bit version > of compat-gcc-34. (Or at least I need to be able to compile 32-bit > binaries with the already available version.) I can't seem to do this; > am I just missing something? > > In retrospect, installing the 64-bit OS may have been foolish. But it's > too late now. I've spent several days installing/loading/configuring > this system to the point it's at now. It would be a pity to have to > start over completely just to enable this one (very critical) function. > > -AlanYou do not provide a lot of detail on what the actual problem is, but have you tried the -m32 flag with gcc. that will tell it to create 32-bit code. You will also need to pass that option to the linker and be sure any dependent libraries have the 32 bit versions installed. -- Jeff
On Tue, Mar 29, 2011 at 6:35 PM, Alan M. Evans <ame1 at extratech.com> wrote:> Ugh. > > One of our internal servers crashed so bad I just went out and bought a > new machine to replace it. > > The old server was Pentium-4 based and running CentOS-5. When I > installed CentOS on the new machine, I used the 64-bit version, partly > because that habit is almost automatic nowadays, and partly because the > new machine has 6GB of RAM, so 32-bit seemed not very appropriate. > > Anyway, I've managed to configure every one of the old server's many > functions to match on the new server but one: I need the 32-bit version > of compat-gcc-34. (Or at least I need to be able to compile 32-bit > binaries with the already available version.) I can't seem to do this; > am I just missing something?Perhaps you can use "mock" to build chroot cages for such 32-bit operations?
Apparently Analagous Threads
- save() with 64 bit and 32 bit R
- Memory issues on a 64-bit debian system (quantreg)
- How to deal with multiple patches to the same file
- Disconnecting: Corrupted MAC on input. - Solaris 8 64-bit SPARC OpenSSH 4.4p1
- R 3.0, Rtools3.0,l Windows7 64-bit, and permission agony