>> Also don't forget us embedded people that are *desperately* trying to >> do native compilations using an NFSroot with limited main memory and >> don't have a disk in the hardware design to swap to. > >Why would you work in such a crippled environment?
Arrrrgh! Believe me, I do as much work on a 3+Ghz 2GbDDR x86 box, but then I'm literally screwed by the plethora of Linux packages that just can't cross build because their configure thinks it can build/run test programs to figure out things like byte ordering, etc. Take perl, zlib, openssh, as an example. Also there are so many interdependencies between packages that we have to build a pile of libraries and support stuff that is never used on the target just so we can get a package that we do need to configure/build(like sed and perl). Until package maintainers take cross-compilation *seriously*, I have no choice but to do native compilation of a large hunk of the packages on eval boards that can literally takes *DAYS* to build. We embedded linux developers have been harping on this for the past couple of years, but no one really takes our problem seriously. Instead we keep getting the "get faster hardware" as the patent cure-all to execution speed problems, but in my case, there is no other hardware I can use. -- Peter Barada [EMAIL PROTECTED]
