**** BEGIN LOGGING AT Tue Sep 29 02:59:58 2015 Sep 29 08:04:17 build #97 of xburst is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/xburst/builds/97 Sep 29 08:10:49 build #102 of cobalt is complete: Failure [failed shell_10] Build details are at http://buildbot.openwrt.org:8010/builders/cobalt/builds/102 Sep 29 08:14:10 build #102 of cns21xx is complete: Failure [failed shell_10] Build details are at http://buildbot.openwrt.org:8010/builders/cns21xx/builds/102 Sep 29 08:17:58 build #102 of orion is complete: Failure [failed shell_10] Build details are at http://buildbot.openwrt.org:8010/builders/orion/builds/102 Sep 29 09:49:45 build #97 of brcm63xx.smp is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/brcm63xx.smp/builds/97 Sep 29 10:31:16 build #101 of pxa is complete: Failure [failed shell_10] Build details are at http://buildbot.openwrt.org:8010/builders/pxa/builds/101 Sep 29 10:49:46 build #92 of cns3xxx is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/cns3xxx/builds/92 Sep 29 11:01:59 build #93 of ath25 is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/ath25/builds/93 Sep 29 11:38:33 jow r47069 trunk/include/prereq-build.mk * prereq-build: test availability of Perl Thread::Queue module Sep 29 11:38:49 jow r47070 trunk/tools/quilt/ patches/000-relocatable.patch Makefile * quilt: add further relocatability fixes Sep 29 12:53:02 saik0: pretty broad area, what are you hoping to do? Sep 29 14:37:41 hello. I'd like to add support for new platform , but I have some constraints - it (at least on the begining) should be based on some particular (older) kernel. Can I do this ? how? is KERNEL_PATCHVER enough to change ? Sep 29 14:47:49 "maybe" Sep 29 14:47:51 how old? Sep 29 14:47:59 2.6.31 Sep 29 14:48:03 forgetaboutit Sep 29 14:48:27 you might get closer by using openwrt-aa or even backfire, Sep 29 14:48:32 and then seeing ifyou can port forward? Sep 29 14:48:46 or, if you ahve the kernel source, see which bits you can bring forward bit by bit? Sep 29 14:49:06 there's a config option to use an entire external kernel tree, probably more use than trying to change just the patchver Sep 29 14:49:11 I know that for some userland tools it might be hard,some are very kernel depended. but what are just general rules to have custom kernel in platform ? Sep 29 14:49:49 o, that would be interesting.. Sep 29 14:50:20 you could have a look at how cerowrt does it and friends, but pretty sure it's by having the entire tree external Sep 29 14:50:26 it's under "Advanced config for developers) Sep 29 14:50:57 yeah, ok . I just recalled, I made this once before this way.. Sep 29 14:51:42 but what if I'd like to start *trying* to have new platform support ? KERNEL_PATCHVER is the right place to start with ? Sep 29 14:53:01 personally, I'd look at what the major differences were in your private tree and teh tree it's based on, see what might be sane, Sep 29 14:53:54 I have patches already prepared (my tree vs this vanilla kernel) Sep 29 14:55:30 later maybe I will port those drivers and changes to some newer kernel. I just need some motivation ;) Sep 29 15:00:35 karlp - I see this external kernel option has made a symlink , like this - 'linux-3.18.21 -> /home/voyo/mr301/linux-2.6.31.8-mr301' , is it ok? should I expect some troubles with this ? Sep 29 15:25:24 * karlp shrugs Sep 29 15:25:50 probably the same problems as the source tree override for packages, make clean will only remove the symlink and so on, which might not be what you want, Sep 29 15:35:44 karlp: remember that openwrt kernels are really patched... Sep 29 15:36:08 also APIs have changed hell a lot, so packet tagging might actually not even compile Sep 29 15:38:43 voyo: ^^ Sep 29 15:40:30 just fighting with default platform config-3.18 vs external kernel. Its not using orginal platform patches, but wants to use this particular config. and 'make kernel_menuconfig' is not helping either Sep 29 15:41:05 I saved my kernel's .config into config-3.18 , so far ok.. target is building. dirty hacks :P Sep 29 15:41:11 I don't think youĂ°'ll have a chance in hell just tryign to point 3.18 directly at 2.6.31 Sep 29 15:41:35 but you could start by looking at junking large chunks of the patches directories :) Sep 29 15:42:45 I did not cleaned everything correctly (user space ), just trying to recompile target/linux . will see what will happend.. Sep 29 15:53:26 so far so good... lets leave it on screen and head to home ;) Sep 29 15:53:29 tnx , bye Sep 29 15:53:35 exit Sep 29 16:05:09 should have left irc on screen too... Sep 29 16:09:58 build #92 of adm8668 is complete: Failure [failed shell_14] Build details are at http://buildbot.openwrt.org:8010/builders/adm8668/builds/92 Sep 29 16:11:38 if that's the mr301 which what google found (lanner mr-301 or wtf) with a 88f6281, then that's a kirkwood Sep 29 16:38:08 they're gone.. Sep 29 16:39:16 i know, just lamenting ;p Sep 29 18:36:01 <_trine> aircrack-ng no longer compiles >>> https://paste.debian.net/313827/ Sep 29 22:10:25 _trine: doesn't look like anybody is jumping to fix it... Sep 29 22:13:24 jow_laptop: any reason not to go w/ px5g SHA1->SHA256 cert sigs? Sep 30 00:38:21 build #89 of mpc52xx is complete: Failure [failed shell_10] Build details are at http://buildbot.openwrt.org:8010/builders/mpc52xx/builds/89 Sep 30 01:55:35 build #101 of ppc40x is complete: Failure [failed shell_10] Build details are at http://buildbot.openwrt.org:8010/builders/ppc40x/builds/101 **** ENDING LOGGING AT Wed Sep 30 02:59:58 2015