[SOLVED] 32-bit support on GCC 4.7.3 for x86_64

rdx · 01-15-2014, 11:09 AM

In order to compiler to 32-bit executables on my 64-bit machine, I apparently need the 32-bit libraries or something. Does anyone know exactly what files I need? I want to get WINE working but it wants 32-bit support. The make fails, not recognizing -m32 flag.

TobiSGD · 01-15-2014, 12:14 PM

Assuming that you use Slackware (you didn't specify which distro use), install the multilib packages from AlienBob to get 32 bit support. When you are at it already you can also use his Wine package, so that you don't need to compile it.

brianL · 01-16-2014, 02:46 AM

See here:
http://docs.slackware.com/slackware:multilib

rdx · 01-17-2014, 05:23 AM

Quote:

Originally Posted by TobiSGD

Assuming that you use Slackware (you didn't specify which distro use), install the multilib packages from AlienBob to get 32 bit support. When you are at it already you can also use his Wine package, so that you don't need to compile it.

Distro? Yes, Slackware. (I guess peeps don't believe the profile info over on the left)

Okay, I went to AlienBOB's and it was FANTASTIC. I followed his simple instructions and everything ran without incident. After so many packages that FAIL, it is a pleasant relief to have something that works as advertised. I'm not sure how to test it.

Drakeo · 01-17-2014, 06:49 AM

test it by running skype

rdx · 01-17-2014, 07:44 AM

Quote:

Originally Posted by Drakeo

test it by running skype

Ummm, thanks but I'm not set up for Skype, I don't have the microphone. I tried Photoshop (fail) and some DOS style games (fail). Games (mmorpg?) are what I use windoz for most and what I'd like to be able to play. Of course browser games are no problem.

brianL · 01-17-2014, 07:57 AM

I tested my multilib setup with a simple "Hello, Brian!" C program:

Code:

bash-4.2$ cd Progs
bash-4.2$ gcc hello.c -o hello64
bash-4.2$ . /etc/profile.d/32dev.sh
bash-4.2$ gcc hello.c -o hello32
bash-4.2$ file hello32
hello32: ELF 32-bit LSB  executable, Intel 80386, version 1 (SYSV), dynamically linked (uses shared libs), not stripped
bash-4.2$ file hello64
hello64: ELF 64-bit LSB  executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), not stripped
bash-4.2$

rdx · 01-18-2014, 03:08 AM

Quote:

Originally Posted by brianL

I tested my multilib setup with a simple "Hello, Brian!" C program:

Code:

bash-4.2$ cd Progs
bash-4.2$ gcc hello.c -o hello64
bash-4.2$ . /etc/profile.d/32dev.sh
bash-4.2$ gcc hello.c -o hello32
bash-4.2$ file hello32
hello32: ELF 32-bit LSB  executable, Intel 80386, version 1 (SYSV), dynamically linked (uses shared libs), not stripped
bash-4.2$ file hello64
hello64: ELF 64-bit LSB  executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), not stripped
bash-4.2$

It seems I've made a pig's breakfast of things. I guess it's obvious that I was confusing WINE with the compiler in trying to test GCC. Using your example above I discovered a mess of my own making. I had been trying to upgrade the compiler to 4.7.3 and 4.8.2 and they are getting mixed up with the original. I'm going too have to clean that mess up before I can proceed because I'm getting all sorts of incompatible files and file not found errors. Thanks for your help, it exposed the problems.
...
Okay, all's well, it works. Thanks again!