From: Ian Lance Taylor <ian@airs.com>
To: "Andrey V. Romanchev" <negative@smartlogic.ru>
Cc: gcc-help@gcc.gnu.org
Subject: Re: Cross compile from i686-pc-linux-gnu to mipsel-linux
Date: Sat, 30 Jul 2005 00:44:00 -0000 [thread overview]
Message-ID: <m34qad5dia.fsf@gossamer.airs.com> (raw)
In-Reply-To: <42EA6F84.9010401@smartlogic.ru>
"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.
If you want to build a cross-compiler which runs on i686-pc-linux-gnu
and generates code which runs on mipsel-linux, then this will suffice:
configure --target=mipsel-linux --prefix=...
Since you are talking about a cross-compiler to a Linux target, I also
recommend looking at
http://kegel.com/crosstool/
> make
> and get the following:
> [skip]
> Configuring in build-i686-pc-linux-gnu/libiberty
> configure: creating cache ../config.cache
> checking whether to enable maintainer-specific portions of Makefiles... no
> checking for makeinfo... makeinfo
> checking for perl... perl
> checking build system type... i686-pc-linux-gnu
> checking host system type... i686-pc-linux-gnu
> checking for i686-linux-ar... no
> checking for ar... ar
> checking for i686-linux-ranlib... no
> checking for ranlib... ranlib
> checking for i686-linux-gcc... gcc
> checking for suffix of object files... configure: error: cannot
> compute suffix of object files: cannot compile
> See `config.log' for more details.
> make: *** [configure-build-libiberty] Error 1
>
> As I understand it tries to configure modules which run on the build
> machine. I am not very competent in gcc compile and I trying to ask
> more able people :)
That said, I don't know what is happening here. If you still want to
figure it out, you should look at the file
build-i686-pc-linux-gnu/libiberty/config.log
(as the error message suggests).
Ian
next prev parent reply other threads:[~2005-07-30 0:44 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 [this message]
2005-07-30 5:53 ` Andrey V. Romanchev
[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=m34qad5dia.fsf@gossamer.airs.com \
--to=ian@airs.com \
--cc=gcc-help@gcc.gnu.org \
--cc=negative@smartlogic.ru \
/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).