build failure - H8/300 - no crt0.o

Jonah gccmail@whalesolutions.ca
Thu Oct 10 14:48:00 GMT 2002


Actually I just had a similar problem today. Something under gcc (libiberty
presumably) tries to build a program using the newly built gcc and the
libraries (inc crt0.o) located in your prefix directory (eg. /usr). The
problem I had was I was building a cross-compiler and had not built the C
library yet on this machine. Once I installed gcc (just ran make install) I
built and installed my C library (newlib), then re-ran make for gcc and it
completed successfully this time.

I hope any (all :-) of this has helped.

BTW I was using arm target building on x86 with cygwin environment using gcc
from the latest snapshot (20021007).

----- Original Message -----
From: "tm" <tm@mail.kloo.net>
To: <gcc-bugs@gcc.gnu.org>
Cc: <kazu@cs.umass.edu>; <law@redhat.com>
Sent: Thursday, October 10, 2002 8:37 PM
Subject: build failure - H8/300 - no crt0.o


>
> host: i386-linux
> target: h8300-elf
>
> GCC fails when building, apparently because of no crt0.o:
>
> ...
> checking for sys/time.h... yes
> checking for time.h... yes
> checking for sys/resource.h... yes
> checking for sys/stat.h... yes
> checking for sys/mman.h... yes
> checking for fcntl.h... yes
> checking for alloca.h... yes
> checking for sys/wait.h that is POSIX.1 compatible... no
> checking whether time.h and sys/time.h may both be included... no
> checking whether errno must be declared... yes
> checking for ANSI C header files... no
> checking for uintptr_t... no
> checking for pid_t... yes
> checking whether the C compiler ( /home/tm/gcc-build-h8300-elf/gcc/xgcc
> -B/home/tm/gcc-build-h8300-elf/gcc/ -B/usr/local/h8300-elf/bin/
> -B/usr/local/h8300-elf/lib/ -isystem /usr/local/h8300-elf/include -O2 -g
> -O2 ) works... no
> configure: error: installation or configuration problem: C compiler cannot
> create executables.
> make: *** [configure-target-libiberty] Error 1
>
> The SH has a crt1.asm, but there is no crt0.asm for the H8/300 -
> is this by omission or intentional?
>
> Toshi
>



More information about the Gcc-bugs mailing list