32 Bit compiling under 64 Bit

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



2010/10/14 Kabil Akp?nar <kabilakpinar at gmail.com>:
> 13 Ekim 2010 16:44 tarihinde Benny Prijono <bennylp at teluu.com> yazd?:
>>
>> 2010/10/13 Kabil Akp?nar <kabilakpinar at gmail.com>:
>> > Yesterday, I had asked the below question but no one could help me. So a
>> > parallel question, in order to cross compile will
>> > "--host=i686-linux-gnu" be
>> > enough for the compilation output 32 bit executables?
>> >
>>
>> I usually just added -m32 to produce 32bit exe. The exe names will
>> still contains "x86_64" but I believe they are 32bit.
>
> Where did you put this compilation switch? I put it for "aconfigure" but, as
> I said before this switch is not passed for executable ones, libraries are
> compiled with this flag though. Please check the former e-mails.

I did read your mails. It doesn't matter where you put it, e.g. you
could do like this:

./aconfigure CFLAGS='-Wno-unused-label -m32' LDFLAGS='-m32'

It's the LDFLAGS that you missed. With this:

$ file pjsua-x86_64-unknown-linux-gnu
pjsua-x86_64-unknown-linux-gnu: ELF 32-bit LSB executable, Intel
80386, version 1...

Without -m32:
pjsua-x86_64-unknown-linux-gnu: ELF 64-bit LSB executable, x86-64, version 1..

Maybe someone else can suggest cleaner options that also fix the output suffix.

 Benny



[Index of Archives]     [Asterisk Users]     [Asterisk App Development]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [Linux API]
  Powered by Linux