How to compile 32-bit programs
Rick Stevens
rstevens at vitalstream.com
Wed Mar 24 23:24:32 UTC 2004
Andrius wrote:
> Thank you for help. I found glibc in my slackware instalion. It doesn't
> replace X86_64 stuff because it is in seperate folders (for example
> lib64 instead of lib).
Ah. I just bought an Opteron (hasn't arrived yet), so I've not done it.
Is your problem fixed now?
> Tr, 2004-03-24 20:45, Rick Stevens rašė:
>
>>Andrius wrote:
>>
>>>I can compile, but I can't link files.
>>
>>First, see if ld has 32-bit emulation. Do "ld --verbose" to see what
>>emulations are supported. I don't have an AMD64 system, but I suspect
>>you need to install the glib*.i386 stuff for that to work. I don't
>>know it that'd replace the glib*.x86_64 stuff or not.
>>
>>FYI, crt1.o is the object file that gets control of a program when it's
>>launched (it provides the "__main()" call which sets up the program's
>>environment, then it calls your "main()" function).
>>
>>
>>>Tr, 2004-03-24 20:23, Andrius rašė:
>>>
>>>
>>>>I can't find how to compile 32-bit programs in fedora for AMD64. (I
>>>>tried g++ -m32 main.cpp but got this "/usr/bin/ld: cannot open crt1.o:
>>>>No such file or directory
>>>>collect2: ld returned 1 exit status").
>>>>
>>>>
>>>
>>>
>>>
>>
>>--
>>----------------------------------------------------------------------
>>- Rick Stevens, Senior Systems Engineer rstevens at vitalstream.com -
>>- VitalStream, Inc. http://www.vitalstream.com -
>>- -
>>- Microsoft Windows: Proof that P.T. Barnum was right -
>>----------------------------------------------------------------------
>>
>
>
>
--
----------------------------------------------------------------------
- Rick Stevens, Senior Systems Engineer rstevens at vitalstream.com -
- VitalStream, Inc. http://www.vitalstream.com -
- -
- "If you can't fix it...duct tape it!" - Tim Allen -
----------------------------------------------------------------------
More information about the users
mailing list