From: Alexey Umnov <umnoff@gmail.com>
To: gcc-help@gcc.gnu.org
Subject: Re: Cross compilation problem
Date: Tue, 27 Mar 2012 06:30:00 -0000 [thread overview]
Message-ID: <CAL2H9vBk=pDEsYbtFP1ptjBudj_miOwj5FH0sihfeO0LoeJ=AA@mail.gmail.com> (raw)
In-Reply-To: <mcrzkb3nl2c.fsf@dhcp-172-18-216-180.mtv.corp.google.com>
>> The problem is that the tools that is being built are not 32bit
>> executables, they are rather 64bit (ELF 64-bit LSB executable,
>> x86-64). This is not what I expected because of
>> "--with-host=i386-linux-gnu" parameter which as far as I understand
>> tells the build system to build a compiler that runs on 32bit linux
>> machine.
>
> Specifying --with-host tells the build system that the resulting
> executables should run on that host. However, you also have to provide
> a compiler that generates executables that run on that host. If you
> don't, the configure script will try to find such a compiler. In your
> case it appears to be getting it wrong.
>
> I would recommend passing BOOT_CFLAGS=-m32 when you run configure and/or
> make.
>
> Ian
Thank You!
I tried to add following parameters and they helped:
--disable-bootstrap CFLAGS=-m32
I also added CFLAGS=-m32 to "make" command just in case
I don't know what exactly made such an effect but the problem is
solved now. Thank You!
----------------------------
Best regards!
Alexey Umnov
umnoff@gmail.com
next prev parent reply other threads:[~2012-03-27 6:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-26 12:25 Alexey Umnov
2012-03-26 20:50 ` Ian Lance Taylor
2012-03-27 6:30 ` Alexey Umnov [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-01-05 21:45 Cross Compilation Problem ebony5146
2000-04-01 0:00 ` ebony5146
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAL2H9vBk=pDEsYbtFP1ptjBudj_miOwj5FH0sihfeO0LoeJ=AA@mail.gmail.com' \
--to=umnoff@gmail.com \
--cc=gcc-help@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).