This is the mail archive of the crossgcc@sourceware.org mailing list for the crossgcc project.
See the CrossGCC FAQ for lots more information.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
What's worked for me is to build the symlink tree pointing at their respective CVS local repositories:
cd $x mkdir combined-tree cd combined-tree ln -s $gcc_source/gcc/* . ln -s $binutils_source/* . >/dev/null 2>&1 rm include;mkdir include;cd include ln -s $gcc_source/gcc/include/* . ln -s $binutils_source/include/* . >/dev/null 2>&1
Then ...
cd $y/buildspace
$x/combined-tree/configure --target=<n> --prefix=<p> <and so on to your taste>
This has worked for me since gcc-3.x/binutils-2.9 (once I got my new triplet straight, that is :-) ).
I'd try it before you start hacking build scripts ... --with-sysroot= was also a godsend for any cross. Once you start hacking build scripts, you'll end up going down some really bizarre paths. Been there, done that.
And the other thing ... maybe Dan's crosstool script handles your target, maybe it doesn't. It might be worth a shot.
------ Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/ Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |