**** BEGIN LOGGING AT Tue May 08 03:00:02 2012 May 08 03:04:15 anyone here know much about the broadcom drivers used in android? bcm4329? May 08 03:04:29 it keeps getting stuck at 1-2mbps connected to my ath9k ap May 08 03:04:37 when i run speed tests on the device i see : /usr/lib/update-notifier/update-motd-fsck-at-reboot May 08 03:04:38 er May 08 03:04:40 :D May 08 03:05:03 wl_iw_event: dev=eth0 event=20 May 08 03:05:30 build #9 of pxcab is complete: Exception [exception shell_2] Build details are at http://buildbot.openwrt.org:8010/builders/pxcab/builds/9 May 08 03:05:31 build #13 of at91 is complete: Exception [exception shell_2] Build details are at http://buildbot.openwrt.org:8010/builders/at91/builds/13 May 08 03:05:32 build #9 of xburst is complete: Exception [exception shell_2] Build details are at http://buildbot.openwrt.org:8010/builders/xburst/builds/9 May 08 03:05:35 build #9 of atheros is complete: Exception [exception shell_2] Build details are at http://buildbot.openwrt.org:8010/builders/atheros/builds/9 May 08 03:05:36 build #10 of lantiq is complete: Exception [exception shell_2] Build details are at http://buildbot.openwrt.org:8010/builders/lantiq/builds/10 May 08 03:05:36 build #12 of brcm47xx is complete: Exception [exception shell_2] Build details are at http://buildbot.openwrt.org:8010/builders/brcm47xx/builds/12 May 08 03:06:22 wifi down/wifi up fixes it nearly always May 08 03:06:37 bringing the wifi down/up on the phone, or cycling power on the phone, does not May 08 03:06:45 no other devices are affected May 08 03:08:25 build #8 of etrax is complete: Exception [exception shell_2] Build details are at http://buildbot.openwrt.org:8010/builders/etrax/builds/8 May 08 03:08:25 build #11 of iop32x is complete: Exception [exception shell_2] Build details are at http://buildbot.openwrt.org:8010/builders/iop32x/builds/11 May 08 03:08:39 build #8 of adm5120 is complete: Exception [exception shell_2] Build details are at http://buildbot.openwrt.org:8010/builders/adm5120/builds/8 May 08 03:08:48 build #8 of ep93xx is complete: Exception [exception shell_2] Build details are at http://buildbot.openwrt.org:8010/builders/ep93xx/builds/8 May 08 03:08:56 build #11 of cobalt is complete: Exception [exception shell_2] Build details are at http://buildbot.openwrt.org:8010/builders/cobalt/builds/11 May 08 03:09:38 build #11 of octeon is complete: Exception [exception shell_2] Build details are at http://buildbot.openwrt.org:8010/builders/octeon/builds/11 May 08 03:10:20 build #8 of rdc is complete: Exception [exception shell_2] Build details are at http://buildbot.openwrt.org:8010/builders/rdc/builds/8 May 08 03:10:21 build #8 of gemini is complete: Exception [exception shell_2] Build details are at http://buildbot.openwrt.org:8010/builders/gemini/builds/8 May 08 03:10:21 build #8 of mpc52xx is complete: Exception [exception shell_2] Build details are at http://buildbot.openwrt.org:8010/builders/mpc52xx/builds/8 May 08 03:11:15 build #10 of ppc44x is complete: Exception [exception shell_2] Build details are at http://buildbot.openwrt.org:8010/builders/ppc44x/builds/10 May 08 03:11:16 build #9 of sibyte is complete: Exception [exception shell_2] Build details are at http://buildbot.openwrt.org:8010/builders/sibyte/builds/9 May 08 03:11:16 build #10 of uml is complete: Exception [exception shell_2] Build details are at http://buildbot.openwrt.org:8010/builders/uml/builds/10 May 08 03:11:31 build #10 of ppc40x is complete: Exception [exception shell_2] Build details are at http://buildbot.openwrt.org:8010/builders/ppc40x/builds/10 May 08 03:11:42 build #10 of x86 is complete: Exception [exception shell_2] Build details are at http://buildbot.openwrt.org:8010/builders/x86/builds/10 May 08 03:12:37 build #9 of ar7 is complete: Exception [exception shell_2] Build details are at http://buildbot.openwrt.org:8010/builders/ar7/builds/9 May 08 03:13:42 build #10 of ar71xx is complete: Exception [exception shell_2] Build details are at http://buildbot.openwrt.org:8010/builders/ar71xx/builds/10 May 08 03:13:42 build #9 of avr32 is complete: Exception [exception shell_2] Build details are at http://buildbot.openwrt.org:8010/builders/avr32/builds/9 May 08 03:14:01 build #10 of ixp4xx is complete: Exception [exception shell_2] Build details are at http://buildbot.openwrt.org:8010/builders/ixp4xx/builds/10 May 08 03:14:02 build #9 of kirkwood is complete: Exception [exception shell_2] Build details are at http://buildbot.openwrt.org:8010/builders/kirkwood/builds/9 May 08 03:14:02 build #10 of au1000 is complete: Exception [exception shell_2] Build details are at http://buildbot.openwrt.org:8010/builders/au1000/builds/10 May 08 03:15:56 build #14 of brcm63xx is complete: Exception [exception shell_2] Build details are at http://buildbot.openwrt.org:8010/builders/brcm63xx/builds/14 May 08 03:15:56 build #10 of ramips is complete: Exception [exception shell_2] Build details are at http://buildbot.openwrt.org:8010/builders/ramips/builds/10 May 08 03:15:56 build #10 of rb532 is complete: Exception [exception shell_2] Build details are at http://buildbot.openwrt.org:8010/builders/rb532/builds/10 May 08 03:15:56 build #11 of orion is complete: Exception [exception shell_2] Build details are at http://buildbot.openwrt.org:8010/builders/orion/builds/11 May 08 10:09:22 I'm trying to setup a python package following examples like pyserial/deluge and so on, but it seems to have problems finding the threading module on the hostpython: http://pastebin.com/VjrqP0PS May 08 10:09:38 I can see the threading module, but not the lowlevel thread module, May 08 10:09:46 this is apparently something from pthreads? May 08 10:10:07 how can I tell my package about pthreads? it does already get installed on the final image, May 08 10:10:23 as running python on the final image can import threading succesfully. May 08 11:30:13 anyone know why on my openwrt lua shell, "=string.char(9/256)" gives a traceback, "integer expected, got number", but it works on the lua on my host system? May 08 11:30:36 seems to fail whenver the result should be 0? May 08 11:58:21 karlp: openwrt Lua has the lnum patchset applied May 08 11:58:57 karlp: that basically introduces an integer number type because being fully double based is inefficient on non-fpu arches May 08 11:59:29 I saw that a year or two ago some stuff was reverted so as to be predictable at the expense of speed/mem, May 08 11:59:33 is this something else? May 08 12:00:21 is there something that can convert the float back into an integer? May 08 12:00:25 yes May 08 12:00:29 math.floor() May 08 12:00:42 string.char(math.floor(9/256)) May 08 12:00:51 everywhere we might ever happen to use a number :| ? May 08 12:01:01 no May 08 12:01:27 only on places that explicitely expect an integer May 08 12:01:45 it's third party code I was hoping not to modify by fixing the lua installation, not patching the code to deal with this special lua May 08 12:02:12 won't work May 08 12:02:22 so it seems. oh well :) May 08 12:02:51 unless we rebuild lua without the lnum, saying we prefer the inefficiency? May 08 12:03:00 not going to happen May 08 12:03:08 the impact is huge May 08 12:03:25 alright then, we'll get patching :) thanks for the info. May 08 12:03:55 any ideas on why my python package can't find the thread module when building? May 08 12:04:10 on the target device import thread works, May 08 12:06:37 probably because the host python build is unthreaded May 08 12:12:06 hm, its probably doable to make lnum more forgiving, e.g. implicit integer casting in places like string.char() May 08 12:12:15 on the other hand the original code relied on undefined behaviour May 08 12:12:56 so "host python" is the python installed in the staging dir, different from my actual python on my host developement machine, May 08 12:13:05 and different from the python that ends up getting built into the owrt image, May 08 12:13:13 yes May 08 12:13:15 that one has threading and works just fine. May 08 12:14:15 is there a way to get the hostpython to have the threads? May 08 12:14:28 most likely May 08 12:15:01 I was reading through all the makefiles I could that used the python-pakage.mk include, but they're all pretty trivial, May 08 12:19:42 should I try the mailing list, see if anyone there knows more about the python packaging? May 08 13:31:13 nbd * r31650 /trunk/ (include/toplevel.mk scripts/feeds): add further countermeasures against the git core.autocrlf option (fixes #9075) May 08 13:31:14 nbd * r31649 /trunk/.gitattributes: add .gitattributes to prevent the git autocrlf option from messing with CRLF/LF in files May 08 13:54:30 build #12 of orion is complete: Exception [exception shell_2] Build details are at http://buildbot.openwrt.org:8010/builders/orion/builds/12 May 08 13:54:33 build #11 of ramips is complete: Exception [exception shell_2] Build details are at http://buildbot.openwrt.org:8010/builders/ramips/builds/11 May 08 13:55:20 build #10 of atheros is complete: Exception [exception shell_2] Build details are at http://buildbot.openwrt.org:8010/builders/atheros/builds/10 May 08 13:55:20 build #11 of lantiq is complete: Exception [exception shell_2] Build details are at http://buildbot.openwrt.org:8010/builders/lantiq/builds/11 May 08 13:55:28 build #10 of pxcab is complete: Exception [exception shell_2] Build details are at http://buildbot.openwrt.org:8010/builders/pxcab/builds/10 May 08 13:55:31 build #14 of s3c24xx is complete: Exception [exception shell_2] Build details are at http://buildbot.openwrt.org:8010/builders/s3c24xx/builds/14 May 08 13:55:35 build #15 of brcm63xx is complete: Exception [exception shell_2] Build details are at http://buildbot.openwrt.org:8010/builders/brcm63xx/builds/15 May 08 13:55:36 build #11 of rb532 is complete: Exception [exception shell_2] Build details are at http://buildbot.openwrt.org:8010/builders/rb532/builds/11 May 08 13:55:46 build #13 of brcm47xx is complete: Exception [exception shell_2] Build details are at http://buildbot.openwrt.org:8010/builders/brcm47xx/builds/13 May 08 13:56:16 build #10 of ar7 is complete: Exception [exception shell_2] Build details are at http://buildbot.openwrt.org:8010/builders/ar7/builds/10 May 08 13:56:19 build #11 of x86 is complete: Exception [exception shell_2] Build details are at http://buildbot.openwrt.org:8010/builders/x86/builds/11 May 08 13:56:26 build #12 of cobalt is complete: Exception [exception shell_2] Build details are at http://buildbot.openwrt.org:8010/builders/cobalt/builds/12 May 08 13:56:27 build #14 of at91 is complete: Exception [exception shell_2] Build details are at http://buildbot.openwrt.org:8010/builders/at91/builds/14 May 08 13:56:33 build #10 of sibyte is complete: Exception [exception shell_2] Build details are at http://buildbot.openwrt.org:8010/builders/sibyte/builds/10 May 08 13:58:02 build #11 of uml is complete: Exception [exception shell_2] Build details are at http://buildbot.openwrt.org:8010/builders/uml/builds/11 May 08 13:58:02 build #12 of iop32x is complete: Exception [exception shell_2] Build details are at http://buildbot.openwrt.org:8010/builders/iop32x/builds/12 May 08 13:58:03 build #11 of ppc44x is complete: Exception [exception shell_2] Build details are at http://buildbot.openwrt.org:8010/builders/ppc44x/builds/11 May 08 13:58:03 build #11 of ixp4xx is complete: Exception [exception shell_2] Build details are at http://buildbot.openwrt.org:8010/builders/ixp4xx/builds/11 May 08 13:58:03 build #10 of kirkwood is complete: Exception [exception shell_2] Build details are at http://buildbot.openwrt.org:8010/builders/kirkwood/builds/10 May 08 13:58:04 build #11 of ppc40x is complete: Exception [exception shell_2] Build details are at http://buildbot.openwrt.org:8010/builders/ppc40x/builds/11 May 08 13:58:18 build #10 of xburst is complete: Exception [exception shell_2] Build details are at http://buildbot.openwrt.org:8010/builders/xburst/builds/10 May 08 13:58:45 build #10 of avr32 is complete: Exception [exception shell_2] Build details are at http://buildbot.openwrt.org:8010/builders/avr32/builds/10 May 08 13:58:47 build #9 of rdc is complete: Exception [exception shell_2] Build details are at http://buildbot.openwrt.org:8010/builders/rdc/builds/9 May 08 13:59:29 build #9 of gemini is complete: Exception [exception shell_2] Build details are at http://buildbot.openwrt.org:8010/builders/gemini/builds/9 May 08 13:59:46 build #11 of ar71xx is complete: Exception [exception shell_2] Build details are at http://buildbot.openwrt.org:8010/builders/ar71xx/builds/11 May 08 13:59:46 build #11 of au1000 is complete: Exception [exception shell_2] Build details are at http://buildbot.openwrt.org:8010/builders/au1000/builds/11 May 08 13:59:51 build #12 of octeon is complete: Exception [exception shell_2] Build details are at http://buildbot.openwrt.org:8010/builders/octeon/builds/12 May 08 13:59:52 build #9 of etrax is complete: Exception [exception shell_2] Build details are at http://buildbot.openwrt.org:8010/builders/etrax/builds/9 May 08 14:00:12 build #9 of adm5120 is complete: Exception [exception shell_2] Build details are at http://buildbot.openwrt.org:8010/builders/adm5120/builds/9 May 08 14:00:20 build #9 of mpc52xx is complete: Exception [exception shell_2] Build details are at http://buildbot.openwrt.org:8010/builders/mpc52xx/builds/9 May 08 14:00:23 build #9 of ep93xx is complete: Exception [exception shell_2] Build details are at http://buildbot.openwrt.org:8010/builders/ep93xx/builds/9 May 08 15:12:16 what is "HostBuild" stuff used for? May 08 15:12:28 building stuff that is supposed to run on the host May 08 15:12:31 as the name implies May 08 15:14:19 hm. is there any limitations in vlan ids on atheros based socs? May 08 15:14:25 so for building a python package, that runs a setup.py, it runs a hostpython, which is not the same as the pythong that ends up ont he target image May 08 15:15:05 ciscos dont like the 0 it seems and use 1 as default. how far up is a reasonably inter-device working range? May 08 15:15:28 first 1k are pretty good, May 08 15:15:42 using the second 3k will have some limits on some older devices, May 08 15:15:58 any limits on the number of vlans? May 08 15:16:14 4k total. then you're out of bits in a dot1q tag. May 08 15:16:33 i planned to use a cisco 3524 in the cellar and loads of tplink741 as vlan switches May 08 15:17:14 sure. i know that. i just remembered something of reading that the small switch chips had limits at 8 or 16 vlans, and could not find any documentation May 08 15:17:40 wel,l yeah, May 08 15:17:52 no, I have no information on how many will be suppoorted May 08 15:22:06 nbd, do you know how to get the hostpython to have threading support? the python built for the target has the thread module, but my PyPackge doesn't build because it aborts when thread isn't found on the hostpython May 08 15:22:31 i don't know much about python May 08 15:22:53 fair enough, do you know who might? May 08 15:22:56 nevermind. found it. May 08 15:22:57 ag71xx_ar7240.c:#define AR7240_MAX_VLANS 16 May 08 15:23:02 roh: vlan ids up to 4096 and 128 concurrent vlan group entries May 08 15:23:03 use the code, luke ;) May 08 15:23:25 ok then only 16 concurrent entries May 08 15:23:35 does not mean that the max vid is 16 though May 08 15:26:09 sure. just making sure i dont need to redeploy different vlan ids later if i can avoid it now. 1-15 or so is fine for now in this building May 08 15:26:32 it had a flat no-vlan structure till now, no reason to go overboard May 08 15:26:35 karlp: HOST_CONFIGURE_ARGS += --with-threads in the OpenWrt python makefile May 08 15:29:38 in mine? or does that have to go in the python makefile itself? May 08 15:34:03 yeah, Host/Configure in feeds/packages/lang/python/Makefile has --without-threads May 08 16:43:52 nunojpg * r31651 /packages/utils/restorefactory/files/uci_defaults_restorefactory: [packages] restorefactory, default configuration file correction May 08 16:44:51 nunojpg * r31652 /packages/utils/watchcat/files/uci_defaults_watchcat: [packages] watchcat, default configuration file correction May 08 18:27:02 If I rsync my trunk build from one system to another how do i get it to work? May 08 18:27:06 /home/scareye/gateworks-cns3xxx-gw2388/staging_dir/toolchain-arm_v6k_gcc-linaro_uClibc-0.9.32_eabi/bin/../libexec/gcc/arm-openwrt-linux-uclibcgnueabi/4.5.4/cc1: error while loading shared libraries: libppl_c.so.4: cannot open shared object file: No such file or directory May 08 18:27:10 make[6]: *** [kernel/bounds.s] Error 1 May 08 18:27:15 do I have to run make clean? May 08 18:31:13 hey, i submitted a patch to add a Makefile for building daemonlogger on OpenWRT - is there anything special i need to do to have it reviewed? May 08 18:31:38 no May 08 18:33:41 how would i go about getting it committed? May 08 18:33:47 you would wait May 08 18:34:14 ah, hehe i figured it was a matter of priorities - looks like you guys get a ton of patches May 08 18:34:21 jow_laptop: any chance of reviewing/committing the dnsmasq scripting changes? thanks... May 08 18:34:23 thanks May 08 18:34:32 philipp64|laptop: chance yes, time no May 08 18:34:47 as long as we're all clamoring to get our patches committed... ;-) May 08 18:35:04 :-p May 08 18:35:10 also, have a replacement for linuxigd which supports igd v2. May 08 18:37:23 isn't miniupnpd the "replacement" May 08 18:40:24 oh, while i'm here... do SVG originals exist for the block diagrams i've seen on the wiki? im getting ready to publish a guide on using openwrt as a network tap (via daemonlogger and some other tricks) and would like to include diagrams May 08 18:40:31 would be nice to not have to start from scratch May 08 18:41:39 i'll also be contributing a block diagram of the WRT150N to the wiki May 08 19:12:48 what block diagrams? May 08 19:13:19 not all are from the same source May 08 19:14:39 nunojpg * r31653 /packages/utils/restorefactory/files/uci_defaults_restorefactory: [packages] restorefactory, correct typo May 08 19:14:44 er, the forums i meant May 08 19:14:49 here's one: https://forum.openwrt.org/viewtopic.php?pid=38549 May 08 19:15:33 no, thats user contributed graphics May 08 19:17:27 what about this: http://wiki.openwrt.org/toh/linksys/wrt54g May 08 19:22:03 gnnh. why does this wl500g not accept my vlan trunks May 08 19:29:17 roh: are you configuring it through /e/c/config or through /proc/switch (or whatever it was) directly? May 08 19:34:27 KanjiMonster: i use uci May 08 19:34:38 i already have a trunk working.. thats whats worrying me May 08 19:35:02 i tried adding a second trunk to a cisco, and it ignored the '2t' from my config completely May 08 19:35:25 i already rebooted since it didnt work on runtime May 08 19:35:56 its a wl500gp, asus May 08 19:37:35 the broadcom switch does not work this way May 08 19:37:45 or rather its setup script May 08 19:37:57 try to use proc/switch May 08 19:38:21 http://pastebin.com/AY38afKV May 08 19:38:57 r18684 kamikaze May 08 19:40:05 looks sane, right? May 08 19:42:49 any idea? May 08 20:20:47 does anyone have the original SVG for this diagram? http://wiki.openwrt.org/toh/linksys/wrt54g May 09 01:26:00 build #12 of ppc40x is complete: Exception [exception shell_2] Build details are at http://buildbot.openwrt.org:8010/builders/ppc40x/builds/12 May 09 01:26:06 build #16 of brcm63xx is complete: Exception [exception shell_2] Build details are at http://buildbot.openwrt.org:8010/builders/brcm63xx/builds/16 May 09 01:26:19 build #12 of rb532 is complete: Exception [exception shell_2] Build details are at http://buildbot.openwrt.org:8010/builders/rb532/builds/12 May 09 01:26:27 build #10 of etrax is complete: Exception [exception shell_2] Build details are at http://buildbot.openwrt.org:8010/builders/etrax/builds/10 May 09 01:26:57 build #12 of ramips is complete: Exception [exception shell_2] Build details are at http://buildbot.openwrt.org:8010/builders/ramips/builds/12 May 09 01:29:02 build #11 of kirkwood is complete: Exception [exception shell_2] Build details are at http://buildbot.openwrt.org:8010/builders/kirkwood/builds/11 May 09 01:29:02 build #11 of sibyte is complete: Exception [exception shell_2] Build details are at http://buildbot.openwrt.org:8010/builders/sibyte/builds/11 May 09 01:29:02 build #11 of pxcab is complete: Exception [exception shell_2] Build details are at http://buildbot.openwrt.org:8010/builders/pxcab/builds/11 May 09 01:29:03 build #12 of ar71xx is complete: Exception [exception shell_2] Build details are at http://buildbot.openwrt.org:8010/builders/ar71xx/builds/12 May 09 01:29:07 build #10 of ep93xx is complete: Exception [exception shell_2] Build details are at http://buildbot.openwrt.org:8010/builders/ep93xx/builds/10 May 09 01:29:08 build #10 of gemini is complete: Exception [exception shell_2] Build details are at http://buildbot.openwrt.org:8010/builders/gemini/builds/10 May 09 01:29:13 build #10 of adm5120 is complete: Exception [exception shell_2] Build details are at http://buildbot.openwrt.org:8010/builders/adm5120/builds/10 May 09 01:29:27 build #10 of mpc52xx is complete: Exception [exception shell_2] Build details are at http://buildbot.openwrt.org:8010/builders/mpc52xx/builds/10 May 09 01:29:33 build #13 of octeon is complete: Exception [exception shell_2] Build details are at http://buildbot.openwrt.org:8010/builders/octeon/builds/13 May 09 01:30:54 build #11 of xburst is complete: Exception [exception shell_2] Build details are at http://buildbot.openwrt.org:8010/builders/xburst/builds/11 May 09 01:31:37 build #11 of atheros is complete: Exception [exception shell_2] Build details are at http://buildbot.openwrt.org:8010/builders/atheros/builds/11 May 09 01:31:38 build #15 of s3c24xx is complete: Exception [exception shell_2] Build details are at http://buildbot.openwrt.org:8010/builders/s3c24xx/builds/15 May 09 01:31:38 build #13 of orion is complete: Exception [exception shell_2] Build details are at http://buildbot.openwrt.org:8010/builders/orion/builds/13 May 09 01:31:38 build #10 of rdc is complete: Exception [exception shell_2] Build details are at http://buildbot.openwrt.org:8010/builders/rdc/builds/10 May 09 01:31:39 build #12 of lantiq is complete: Exception [exception shell_2] Build details are at http://buildbot.openwrt.org:8010/builders/lantiq/builds/12 May 09 01:31:40 build #12 of ixp4xx is complete: Exception [exception shell_2] Build details are at http://buildbot.openwrt.org:8010/builders/ixp4xx/builds/12 May 09 01:31:41 build #14 of brcm47xx is complete: Exception [exception shell_2] Build details are at http://buildbot.openwrt.org:8010/builders/brcm47xx/builds/14 May 09 01:31:44 build #11 of ar7 is complete: Exception [exception shell_2] Build details are at http://buildbot.openwrt.org:8010/builders/ar7/builds/11 May 09 01:31:54 build #12 of x86 is complete: Exception [exception shell_2] Build details are at http://buildbot.openwrt.org:8010/builders/x86/builds/12 May 09 01:32:05 build #12 of uml is complete: Exception [exception shell_2] Build details are at http://buildbot.openwrt.org:8010/builders/uml/builds/12 May 09 01:32:15 build #11 of avr32 is complete: Exception [exception shell_2] Build details are at http://buildbot.openwrt.org:8010/builders/avr32/builds/11 May 09 01:32:20 build #12 of ppc44x is complete: Exception [exception shell_2] Build details are at http://buildbot.openwrt.org:8010/builders/ppc44x/builds/12 May 09 01:32:55 build #13 of iop32x is complete: Exception [exception shell_2] Build details are at http://buildbot.openwrt.org:8010/builders/iop32x/builds/13 May 09 01:35:04 build #15 of at91 is complete: Exception [exception shell_2] Build details are at http://buildbot.openwrt.org:8010/builders/at91/builds/15 May 09 01:55:24 Exception my face :P May 09 02:07:27 meh. me stupid. forgot to tell it my device m-) May 09 02:31:05 build #12 of kirkwood is complete: Failure [failed compile_4] Build details are at http://buildbot.openwrt.org:8010/builders/kirkwood/builds/12 May 09 02:33:06 build #13 of ixp4xx is complete: Failure [failed compile_4] Build details are at http://buildbot.openwrt.org:8010/builders/ixp4xx/builds/13 May 09 02:36:43 build #12 of sibyte is complete: Failure [failed compile_4] Build details are at http://buildbot.openwrt.org:8010/builders/sibyte/builds/12 **** ENDING LOGGING AT Wed May 09 02:59:58 2012