Hello Jonas!
there is probably a better way to do this, but it should be possible to > make a local overlay and modify the ebuild's src_compile to do emake in > the Cross directory. > > http://devmanual.gentoo.org/ebuild-writing/index.html > > So far this seems to me to be the most reasonable way. I would like to stick to the gentoo way of doing cross compilation, even if it encounters some minor hacks. I'll try it, thanks for pointing me there. > are you documenting your progress somewhere? Nope, but for quite a while I'm considering to put up some blog (or something on google sites)... > can you please point me to > the documents that helped you put together the cross compilation > toolchain? > In fact only embedded gentoo documentation<http://www.gentoo.org/proj/en/base/embedded/>and trial and error method. I succeeded with crossdev --b 2.21.1 --g 4.5.3 --l 2.11.3 --k 2.6.36 -t arm-none-linux-gnueabi which compiled succesfully and created toolchain that can create binaries compatible with my Netgear Stora. So far I haven't tried emerged packages as I am not sure if they will run unless built statically, but sample C program compiled with cross compiler runs ok. > that actually sounds like it successfully cross-compiled try.c, but > *of course* it does not run on your host platform! that check is > probably omitted in Cross/Makefile which might why they are telling you > to run that one. > I agree, I hope I can make some workaround in a short time for that. Using my own overlay seems to be the most appropriate way, I'll write back as soon as I have working ebuild limited to arm architecture... Peter
