Dear Paul Mundt, In message <20090102095023.GA28078@xxxxxxxxxxxx> you wrote: > > Your main reasons against inclusion of perl seem to be that there is no > realistic expectation for target systems that will be self-hosting will > have perl included, or the inherent complexity in maintaining a coherent > cross compiling environment. Both of these things are issues with your > own environment, and in no way are these representative of the embedded > development community at large. I'm not sure how representative for the "embedded development community at large" your statement is. Just to add a data point to the statistice, I do agree with Rob's opinion about needing Per to build the Linux kernel. All other arguments aside, natively compiling the Linux kernel on a target board, especially with root file system mounted over NFS, has always been an excellent stress test (you may even call it regression test) for Linux running on some target hardware. Losing this ability just because some scripts are implemented in language FOO when plain shell will do as well is something we should try to avoid. Of course, YMMV. Best regards, Wolfgang Denk -- DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@xxxxxxx Include the success of others in your dreams for your own success. -- To unsubscribe from this list: send the line "unsubscribe linux-embedded" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
