Strange problems with combined-tree builds

[Dara Hazeghi <dhazeghi at yahoo dot com>]

Hello,

Using a combined tree (binutils, newlib, gcc), to
build a cross to mcore-elf (though it has happened
sporadically for other targets too), I get this at a
certain point:

/home/dara/mainline/objdir/gcc/xgcc
-B/home/dara/mainline/objdir/gcc/ -nostdinc
-B/home/dara/mainline/objdir/mcore-elf/newlib/
-isystem
/home/dara/mainline/objdir/mcore-elf/newlib/targ-include
-isystem
/home/dara/mainline/combined/newlib/libc/include
-B/tmp/dara/mcore-elf/bin/ -B/tmp/dara/mcore-elf/lib/
-isystem /tmp/dara/mcore-elf/include -isystem
/tmp/dara/mcore-elf/sys-include
-L/home/dara/mainline/objdir/ld -O2 -g -O2 -O2 -g -O2
foo.c 
/home/dara/mainline/objdir/gcc/collect-ld: cannot open
crt0.o: No such file or directory

This is after creating a symlinked source directory
and building with just ../combined/configure
--target=mcore-elf. 

It looks like crt0.o is not being built at the proper
time, since when I do a search for it, it doesn't
exist (yet). Yet newlib is definitely build (libc.a
and libm.a exist).

Any suggestions? Thanks,

Dara

__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com

------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com