"Andrey V. Romanchev" <negative@xxxxxxxxxxxxx> 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
