Am Samstag, 7. August 2010, 23:24:03 schrieb Andrew: > 07.08.2010 23:35, KP Kirchdoerfer пишет: > > That's similar to your list above. I can add quagga and nut, both failed > > with the 2.6.32 kernel in a full build a few days ago. > > Strange, quagga and nut are built in my environment OK.
Some of these pb's are related to missing programs on my build host - buildenv is not self-contained. E.g. I solved quagga build with installing gawk. > > BUT what I consider as showstoppers are the impossibilty to compile a > > kernel with a different config as I reported yesterday, the pb's with > > WLAN and ath5k I observe - if you can confirm it's a local problem I > > have, it will be fine with me. > > I also have trouble with ath5k & LEAF - let's look how it'll be on new > kernel... I think I find solution to compile it for i586 with current > binutils - because binutils upgrade looks like harder task which may > cause headache in other packages. I can confirm that I was able a kernel for Geode today, as you wrote this morning. I'll try to upgrade my router to the latest version ASAP. > > Also I'd like to ask again, if we shouldn't target to be ipv6-ready from > > the start - that means to get rid of the seperate ipv6 packages wherever > > possible (for example to have one shorewall.lrp with shorewall and > > shorewall6 instead of two lrp's, moddb.lrp and moddb6.lrp and so on). > > Is it really actually to have IPv6 support for every configuration? IMHO > now in many cases IPv6 modules will just waste space. I believe in two years ipv6 will be a usual demand. Given the slow pace of adoption of a new major release, thinking two yrs into the future is IMHO reasonable. We started to provide ipv6 support years ago - sometimes as seperate packages, but more often ipv6 support is compiled into the currently build packages by configuration settings. So either we waste space in the latter packages, or we waste time for maintenance and administration with the divided packages. As we make huge changes right now (discontinue floppy support, kernel, uClibc, udev), and therefor making a real cut, moving forward to consolidate the remaining splitted packages into a ipv6-ready-form the-start router seems a logic and consequent step to me. kp ------------------------------------------------------------------------------ This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev _______________________________________________ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
