**** BEGIN LOGGING AT Sun Jul 27 03:00:00 2014 Jul 27 03:13:40 build #133 of bcm53xx is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/bcm53xx/builds/133 Jul 27 03:44:33 build #587 of kirkwood is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/kirkwood/builds/587 Jul 27 05:08:00 build #677 of cobalt is complete: Failure [failed compile_5] Build details are at http://buildbot.openwrt.org:8010/builders/cobalt/builds/677 Jul 27 05:24:21 build #131 of mpc83xx is complete: Failure [failed shell_14] Build details are at http://buildbot.openwrt.org:8010/builders/mpc83xx/builds/131 Jul 27 05:35:16 build #130 of cns3xxx is complete: Failure [failed compile_5] Build details are at http://buildbot.openwrt.org:8010/builders/cns3xxx/builds/130 Jul 27 06:51:24 build #132 of pxa is complete: Failure [failed compile_5] Build details are at http://buildbot.openwrt.org:8010/builders/pxa/builds/132 Jul 27 09:30:17 cyrusff, apologies, might be a problem with my Arch Linux, perhaps some updates these days broke something, i tested on both a iMac and a Android tablet and dual stack is okay Jul 27 09:32:54 hmm, but weird, few weeks old trunk still works, i remember tested it last night, same arch linux laptop, so it still might be a problem towards linuxes Jul 27 10:28:45 build #243 of imx6 is complete: Failure [failed shell_3] Build details are at http://buildbot.openwrt.org:8010/builders/imx6/builds/243 Jul 27 10:42:44 build #345 of mpc85xx is complete: Failure [failed shell] Build details are at http://buildbot.openwrt.org:8010/builders/mpc85xx/builds/345 Jul 27 12:18:40 build #637 of ppc44x is complete: Failure [failed shell_9] Build details are at http://buildbot.openwrt.org:8010/builders/ppc44x/builds/637 Jul 27 13:23:39 build #606 of sibyte is complete: Failure [failed shell_9] Build details are at http://buildbot.openwrt.org:8010/builders/sibyte/builds/606 Jul 27 13:28:52 build #648 of uml is complete: Failure [failed compile_5] Build details are at http://buildbot.openwrt.org:8010/builders/uml/builds/648 Jul 27 14:19:03 build #618 of avr32 is complete: Failure [failed compile_5] Build details are at http://buildbot.openwrt.org:8010/builders/avr32/builds/618 Jul 27 14:54:23 blogic r41843 trunk/toolchain/gcc/ Config.in Config.version * octeon: select gcc 4.6 by default Jul 27 14:54:28 blogic r41844 trunk/target/linux/octeon/base-files/lib/functions/octeon.sh * octeon: add detection for edgerouter and edgerouter-pro Jul 27 14:54:34 blogic r41845 trunk/target/linux/octeon/patches-3.10/130-gpio.patch * octeon: add gpio driver Jul 27 14:54:40 blogic r41846 trunk/target/linux/octeon/config-default * octeon: enable usb and gpio Jul 27 17:35:15 updated openwrt/upstream, https://home.comcast.net/~sdwalker/uscan/index.html Jul 27 17:37:47 build #683 of orion is complete: Failure [failed compile_8] Build details are at http://buildbot.openwrt.org:8010/builders/orion/builds/683 Jul 27 17:39:53 build #543 of iop32x is complete: Failure [failed shell_9 shell_14] Build details are at http://buildbot.openwrt.org:8010/builders/iop32x/builds/543 Jul 27 17:47:08 jogo r41847 trunk/target/linux/ (6 files in 5 dirs) * brcm63xx: Add support for Comtrend VR-3025u Jul 27 17:47:10 jogo r41848 trunk/target/linux/ (6 files in 5 dirs) * brcm63xx: Add support for Comtrend VR-3025un Jul 27 17:47:13 jogo r41849 trunk/tools/firmware-utils/ Makefile src/zyxbcm.c * firmware-utils: add new tool for fixing headers on ZyXEL devices (brcm63xx) Jul 27 17:47:15 jogo r41850 trunk/target/linux/ (6 files in 5 dirs) * brcm63xx: Add support for ZyXEL P870HW-51a v2 Jul 27 17:47:18 jogo r41851 trunk/target/linux/ (5 files in 5 dirs) * brcm63xx: Add support for Huawei HG520v Jul 27 17:47:21 jogo r41852 trunk/target/linux/ (7 files in 5 dirs) * brcm63xx: Add support for ADB P.DG A4001N Jul 27 19:31:31 thanks KanjiMonster :D Jul 28 00:17:20 build #637 of rb532 is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/rb532/builds/637 Jul 28 00:18:31 i'm maintaining a package that depends on stack smashing protection (ssp), and can also be built without it Jul 28 00:18:55 if people always build the firmware on their own, or i ship images, that's fine Jul 28 00:19:30 but installation using opkg is tricky, because you might be installing the ssp-enabled version of the package into a system that doesn't have ssp Jul 28 00:20:12 so i'm thinking about making it a metapackage that depends on either -ssp or -nossp Jul 28 00:20:46 any idea how i could query CONFIG_SSP_SUPPORT within the target system? Jul 28 00:20:54 or should i rather check for whether libssp is present? Jul 28 02:06:32 lgierth: How about adding "+SSP_SUPPORT:libssp" to DEPENDS? Jul 28 02:07:30 yep that's what i'm doing right now, i am just wondering if the evaluation of SSP_SUPPORT will happen during opkg install as well Jul 28 02:07:38 when building images it works fine Jul 28 02:08:10 with the -ssp and -nossp packages, it'd be e.g. +SSP_SUPPORT:cjdns-nossp Jul 28 02:08:59 understand what i mean? Jul 28 02:10:12 the basic premise is that we want to make use of ssp whereever it's available, and recommend users who are willing to build their own image to enable SSP_SUPPORT Jul 28 02:11:24 now we want to offer prebuilt packages for `opkg install`, and there we want to detect whether libssp is present (i.e. the image was built using SSP_SUPPORT), so that we can pick the -ssp package wherever possible **** ENDING LOGGING AT Mon Jul 28 03:00:00 2014