Re: Getting closer (was Re: cross-compiler build: can't find stdio.h)

["John Breen" <jab3 at hotmail dot com>]

From: Bill Currie <bcurrie@tssc.co.nz>
>Yeah, it means (most likely) that you don't have a libc.a (or .so)
>for your target.  Check config.log in the directory to be sure.  I
>had this problem too.  If you *do* have libc available, your will
>want to use --with-libs=... to say where it is.

Thanks for the tip (I didn't know there was a config.log).  Here's the 
tail of it:
----------------
configure:622: /data/ecad_libs/egcs/build-m68k/gcc/xgcc \
    -B/data/ecad_libs/egcs/build-m68k/gcc/ -o conftest -g \
    conftest.c  1>&5
/data/ecad_libs/contrib/m68k-elf/bin/ld: cannot open crt0.o: No such
    file or directory
collect2: ld returned 1 exit status
configure: failed program was:
#line 618 "configure"
#include "confdefs.h"
main(){return(0);}
----------------

So you were close: it's crt0.o that's missing.  Obviously I don't have a 
crt0.o, since I don't have a compiler yet (to answer your previous 
question, this is for an in-house developed embedded system; all I have 
for headers and libs is what comes in egcs or newlib).

I could copy over the m68k crt0.S from newlib and see if I can assemble 
it myself with what's there, but should I really have to do things like 
that?
--
John A. Breen
jab3@hotmail.com


______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com