Hinko Kočevar wrote: > John Crispin wrote: >>> What is the etrax status in openwrt? Does it use generated uclibc toolchain >>> or >>> vendor (Axis) provided glibc toochain? >> i can run the generated images on a foxboard, only draw back is, that >> the head.S in kernel needs to be compiled with the axis toolchain. >> using the stage3 elf compiler, it compiles, but wont boot. i gave up >> last week after several hours, trying to figure out whats wrong. > > Did you use cris-elf generated with my patch? > So it seems that uclibc cris-elf is broken:( I had similar problems, but > didn't > try the axis-elf + uclibc-linux combo to make bootable image - I was leaning > more towards the complete dump of Axis toolchain... > > So I guess that uClibc port of cris is mostly up2date in uClibc 0.9.29 (read > working:). > >> as i have time i will continue. at least axis has started to clean up >> all the totally broken upstream code. so lets hope that soon there will >> be a way to compile images using a bog standard gcc > > Yes, it was about time! Too bad they didn't push all the changes to the > upstream > earlier - now we are stuck with some ancient software and transition to newer > versions wouldn't always be a pain in the a..! > > I'll go back a step and to generate correct cris-elf, sometime.. >
yes, the cris-elf seems the problem. if we have a cris-elf that can translate a head.S in to a working bin, then i can get the rest running in no time. but until then you need the axis toolchain installed so we can use their gcc_cris -melf _______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
