Peter M <peter.mdk <at> gmail.com> writes:
>
> Hello scratch box developers,
>
> My short term goal is to get hold of a static binary of tcpdump for
> powerpc 405.
> I tried to follow wangji's recent mail about on how to build a
> crosstool toolchain inside the HOST target. But using the host
> toolchain scratchbox-toolchain-i686-gcc3.3-glibc2.3 1.0.2 the
> demo-ppc405.sh stops with an error when building libiberty saying
> something like I should use --host instead of --build. Outside of
> scratchbox the demo-ppc405.sh script just works.
>
> Then I thought I could copy my working crosscompiler into
> /scratchbox/compilers/powerpc-405-gcc-3.4.1-glibc-2.3.3/ and created
> the 3 files: compiler-name, gcc.specs, target_setup.sh
> [sbox-powerpc-405: ~] > cc
> sbox-powerpc-405--cc: No such file or directory
> [sbox-powerpc-405: ~] >
>
> Note the double dash between 405 and cc.
>
> Any suggestions and help would be greatly appreciated!
> Regards
> Peter M
>
hi,
the host-gcc does give problem !you should try to manually build the
toolchain doing with binutils,then add PATH to those new stuff,
then try to copy libs,include,
what you have done with crosstool outside scratchbox,then go back
to scratchbox and continue compile gcc !!!!
The test is ,when all seem to be there,you just execute from inside
scratchbox, do
[sbox-urppc> gcc -v ,if it is recognised...you are almost 3/4 done !
the ar,as,gcc stuffs are harded coded to where it was built,no way to
build outside , then copy to sbox;you will never be able to get
gcc-wrapper catch in
I recently succeed that way even with mipsel-uclibc-openwrt-buildtree !
good luck ,
wj
_______________________________________________
Scratchbox-devel mailing list
[email protected]
http://lists.scratchbox.org/cgi-bin/mailman/listinfo/scratchbox-devel
