11.02.2012 20:02, KP Kirchdoerfer пишет: > Am 11.02.2012 18:46, schrieb Andrew: >> 11.02.2012 19:28, KP Kirchdoerfer пишет: >>> Am 07.02.2012 18:40, schrieb Andrew: >>>> 07.02.2012 19:30, KP Kirchdoerfer пишет: >>>>> Hi Andrew; hi all, >>>>> >>>>> I've updated on my local host the Linux kernel to 3.2.4 for the >>>>> Bering-uClibc next branch. >>>>> >>>>> The configs are more or less the same as with our current production >>>>> release and requires definitly further review. >>>>> >>>>> To get it build changes to buildpacket.pl and Mastermakefile are >>>>> required, as well as the usual changes to buildtool.cfg|mk of linux and >>>>> kernel package. >>>>> >>>>> While the kernel builds fine after these changes I ran into major >>>>> problems with iptables build. Upgrading to latest upstream does not help. >>>>> >>>>> The first error I ran into was some unknown types in >>>>> include/linux/types.h - I think I solved those with a patch found in the >>>>> openwrt repository, but then I ran into a new build error of iptables, >>>>> where I'm lost even after two days of investigation. >>>>> >>>>> " AR libext4.a >>>>> AR libext6.a >>>>> CHECK unknown symbols in .so files >>>>> /bin/bash: error while loading shared libraries: libdl.so.0: cannot open >>>>> shared object file: No such file or directory" >>>>> >>>>> >>>>> I refused to commit the changes I've made yet, cause it will break the >>>>> next branch completly. But then I run out of ideas what to do get >>>>> iptables build again. >>>>> >>>>> Shall I commit what I've accomplished yet, even it breaks the >>>>> next-version, so you have start to investigate the iptables pb? >>>>> >>>>> kp >>>>> >>>>> >>>> Hi. >>>> You can make new, ''next-experimental' branch for that case. I planned >>>> to update kernel and related packages after finishing config review - if >>>> we don't want to do unnecessary work twice. >>> Hi Andrew; >>> >>> done (next-experimental), made some more updates (iproute, >>> xtables-addons) and the only packages currently failing to build are: >>> iscsi, accel-pptp (and still dhcpcd). >>> >>> May I ask you to merge it to next branch as soon as you are statisfied >>> with your buildconf review? >>> >>> kp >>> >> Ok. Accel-pptp isn't assembled due to kernel driver (in 3.2. there ara >> built-in pptp kernel driver). About iscsi - I'll look on it. >> >> About dhcpcd - maybe you mean dhcpd? Because dhcpcd on my host is >> assembled OK. > Hello; > > Sorry, of course I meant dhcpd - the "good old package, that never > worked for next" :) > Can you also have a look into kernel configs (but shurely they'll > finally improve over time and with more testing, as usual) and the > kernel patches (are some unnecessary with the new kernel?)? Of course I'll look what is changed in kernel (possible points of interest - network drivers - their options were changed structure; xtables/netfilter plugins and so on). > > As you know, I had success with "next" (kernel 2.6.x) on an Alix board > (though not the WIFI part), will do that again, once kmodules will build > again (fails currently due to accel-pptp). > > What shall happen with accel-pptp? > > kp > It'll use kernel module.
------------------------------------------------------------------------------ Virtualization & Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ _______________________________________________ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
