From: "Andrey V. Romanchev" <negative@smartlogic.ru>
To: gcc-help@gcc.gnu.org
Subject: Re: Cross compile from i686-pc-linux-gnu to mipsel-linux
Date: Sat, 30 Jul 2005 05:53:00 -0000 [thread overview]
Message-ID: <42EB18AD.1010103@smartlogic.ru> (raw)
In-Reply-To: <m34qad5dia.fsf@gossamer.airs.com>
Ian Lance Taylor wrote:
> "Andrey V. Romanchev" <negative@smartlogic.ru> writes:
>
>
>>I trying to build gcc for mipsel-linux architecture.
>>CC=mipsel-linux-gcc CFLAGS="-Os -mips32 -mtune=4kc"
>>../gcc-3.4.3/configure --host=mipsel-linux --target=mipsel-linux
>>--build=i686-linux --prefix=/home/me/work/compiling/gcc/build-gcc
>
>
> This is not doing what I would call a cross-compiler from
> i686-pc-linux-gnu to mipsel-linux. I would call this building a
> native compiler for mipsel-linux, and doing the build on
> i686-pc-linux-gnu.
Yes. It exactly what I need - native mipsel-linux compiler.
Is there any docs or any hints for this?
next prev parent reply other threads:[~2005-07-30 5:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-29 17:52 Andrey V. Romanchev
2005-07-30 0:44 ` Ian Lance Taylor
2005-07-30 5:53 ` Andrey V. Romanchev [this message]
[not found] ` <42EB17E4.4040509@smartlogic.ru>
[not found] ` <m3u0ic4xxg.fsf@gossamer.airs.com>
2005-07-30 8:17 ` Andrey V. Romanchev
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=42EB18AD.1010103@smartlogic.ru \
--to=negative@smartlogic.ru \
--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).