hello all. found couple of issues on the way while building mips64 target (on both 8.0 and trunk-r30450). .1 has anybody noticed incorrect options handling in scripts/Download with -mirror, -nock -all/-required? (not mips specific anyway!) .2 the perl build fails on cross build; is the Makefile patch for using 'miniperl' and 'HOST_CC' required? .3 do those pciaccess, alsa-utils and the further dependancies build correctly? may be small issues, but makes me wonder has anybody used T2 to build mips64 target out-of-box?:-)
with this background let me put my intentions: i'm actually evaluating T2 for a new target/architecture that we are designing. the Dietlibc hasn't been ported+built and intend to use glibc/newlib all the way. please excuse if this is a naive question: is it possible to build a Generic, Embedded, and rescue targets without Dietlib? any info/help and advice in this regards will be greatly appreciated! many thanks. girish.
----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to [email protected] with a subject of: unsubscribe t2
