This is the mail archive of the
gcc-help@gcc.gnu.org
mailing list for the GCC project.
Configuring a cross-compiling gcc
- From: The Arrow <arrow at pileborg dot org>
- To: gcc-help <gcc-help at gcc dot gnu dot org>
- Date: Thu, 23 Oct 2003 07:38:27 +0200
- Subject: Configuring a cross-compiling gcc
- Organization: Team Evil
I have a "hypotethical" question...
Lets say I'm making a new operating system (called somenewos), and want
to use GCC to create this new os, and that it will be created by cross-
compiling from a Linux host.
The parameters to the configure script are:
--enable-languages=c,c++ \
--prefix=/some/prefix/toolchain \
--target=i386-somenewos-elf
I have used the same parameters to binutils (without the --enable-
languages of course) and it worked ok. It also seems to work ok for GCC
initially. However, when I try to compile GCC I get some configuration
errors when trying to configure i386-somenewos-elf/libiberty. When
looking in i386-somenewos-elf/libiberty/config.log, this error is at the
bottom:
/some/prefix/toolchain/i386-somenewos-elf/bin/ld: cannot open crt0.o: No
such file or directory
So, my question is: What should I do to get past this? Should I create a
crt0.o and in that case what does GCC need it to do, and where should I
place it? Am I missing some parameters to the top-level configure
script?
I'm using binutils-2.14.90.0.6 and GCC 3.3.2, and this "hyptethical" new
OS is supposed to be made for a normal consumer PC and not an embeded
target.
Thanks in advance.
/ Joachim
--
======================================================================
The Arrow http://www.pileborg.org/~arrow/
Joachim Pileborg Moses @ ptmud.pileborg.org 1111
======================================================================