**** BEGIN LOGGING AT Mon May 26 03:00:00 2014 May 26 03:21:00 <5EXAA8SU8> build #69 of pxa is complete: Failure [failed compile_5] Build details are at http://buildbot.openwrt.org:8010/builders/pxa/builds/69 May 26 04:05:31 <5EXAA8SU8> build #285 of mpc85xx is complete: Failure [failed shell] Build details are at http://buildbot.openwrt.org:8010/builders/mpc85xx/builds/285 May 26 06:21:12 <5EXAA8SU8> build #527 of kirkwood is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/kirkwood/builds/527 May 26 06:21:21 looks like libftdi + boost is maybe the problem, when boost wasn't found (a few weeks ago), libftdi built without error May 26 06:21:55 config script is finding boost --> fall-down-go-boom May 26 06:44:36 confirmed, if i package/boost/clean package/libftdi/{clean,compile}, then libftdi builds okay May 26 07:01:11 _trine: check out the ngircd patch I sent to the mailing list - it should fix your issue with broken build of v21.1 May 26 07:24:55 <5EXAA8SU8> build #651 of brcm63xx is complete: Failure [failed compile_8] Build details are at http://buildbot.openwrt.org:8010/builders/brcm63xx/builds/651 May 26 07:25:09 <5EXAA8SU8> build #630 of brcm47xx is complete: Failure [failed compile_8] Build details are at http://buildbot.openwrt.org:8010/builders/brcm47xx/builds/630 May 26 07:25:33 no space left on device <3 May 26 07:29:47 <5EXAA8SU8> build #70 of adm8668 is complete: Failure [failed shell compile_5] Build details are at http://buildbot.openwrt.org:8010/builders/adm8668/builds/70 May 26 07:34:57 http://patchwork.openwrt.org/patch/5509/ May 26 07:43:32 russell--: did you try to disable --enable-libftdipp" : enable libftdi C++ wrapper. Needs boost (default: auto)] according to configure.ac of libftdi May 26 07:46:44 plntyk: no, the cmake knobs are somewhat alien to me May 26 08:03:31 nbd r40860 trunk/package/kernel/mac80211/Makefile * ath9k: fix deprecated syntax in config symbol May 26 11:37:56 <5EXAA8SU8> build #71 of mpc83xx is complete: Failure [failed compile_8] Build details are at http://buildbot.openwrt.org:8010/builders/mpc83xx/builds/71 May 26 13:55:17 nbd r40861 trunk/package/libs/libubox/Makefile * libubox: update to latest version, fixes a segfault on json_script cleanup May 26 15:27:38 is a "correct" scriptable way to read the machine type? (what shows up in /proc/cpuinfo ?) May 26 15:27:45 or a model name if it's available? May 26 15:38:24 uname -m May 26 15:39:00 that just shows "mips" May 26 15:40:27 you can parse /proc/cpuinfo then May 26 15:41:04 grep '^system type' /proc/cpuinfo|cut -d ':' -f2 May 26 15:46:30 yeah, that's what I've got, I was wondering if there was a "better" way, like, whatever went into /proc/cpuinfo May 26 15:48:23 i don't think there is a better way May 26 15:57:38 VSZ doesn't reallllly matter right? that can just be memory mapped files? I shouldn't have to be terribly concerned if a process has a high percentage in VSZ? May 26 16:02:52 karlp: right May 26 17:10:26 cyrus r40862 trunk/package/network/services/odhcpd/Makefile * odhcpd: add support for configuring raw dhcpv6 options May 26 17:39:44 <5EXAA8SU8> build #576 of ppc44x is complete: Failure [failed shell_10] Build details are at http://buildbot.openwrt.org:8010/builders/ppc44x/builds/576 May 26 17:40:35 <5EXAA8SU8> build #545 of sibyte is complete: Failure [failed shell_10] Build details are at http://buildbot.openwrt.org:8010/builders/sibyte/builds/545 May 26 17:40:36 <5EXAA8SU8> build #576 of rb532 is complete: Failure [failed shell_10] Build details are at http://buildbot.openwrt.org:8010/builders/rb532/builds/576 May 26 17:43:00 <5EXAA8SU8> build #483 of iop32x is complete: Failure [failed shell shell_10] Build details are at http://buildbot.openwrt.org:8010/builders/iop32x/builds/483 May 26 18:25:06 luka r40863 packages/admin/debootstrap/ patches/100-busybox_fix.patch Makefile * [packages] debootstrap: bump version to 1.0.60~bpo70+1 May 26 18:31:18 <5EXAA8SU8> build #511 of au1000 is complete: Failure [failed compile_5] Build details are at http://buildbot.openwrt.org:8010/builders/au1000/builds/511 May 26 19:02:40 <5EXAA8SU8> build #616 of cobalt is complete: Failure [failed compile_5] Build details are at http://buildbot.openwrt.org:8010/builders/cobalt/builds/616 May 26 19:03:07 <5EXAA8SU8> build #622 of orion is complete: Failure [failed compile_5] Build details are at http://buildbot.openwrt.org:8010/builders/orion/builds/622 May 26 19:08:42 <5EXAA8SU8> build #586 of uml is complete: Failure [failed shell compile_5] Build details are at http://buildbot.openwrt.org:8010/builders/uml/builds/586 May 26 19:48:35 hi all! May 26 19:48:44 nbd are you here ? May 26 19:49:28 i see in device.c some mac address assignation code but i didn't uderstood if i have to do something in vlanad.c to permit macaddres changing or not May 26 19:49:56 because at moment macaddress isn't changed also if you set it with option macaddr in device or interface section May 26 20:23:03 <5EXAA8SU8> build #471 of mcs814x is complete: Failure [failed shell compile_5] Build details are at http://buildbot.openwrt.org:8010/builders/mcs814x/builds/471 May 26 20:30:56 <5EXAA8SU8> build #556 of avr32 is complete: Failure [failed compile_5] Build details are at http://buildbot.openwrt.org:8010/builders/avr32/builds/556 **** ENDING LOGGING AT Tue May 27 02:59:58 2014