**** BEGIN LOGGING AT Thu Sep 26 02:59:59 2013
Sep 26 03:08:22 <builder> build #391 of atheros is complete: Failure [failed compile_4]  Build details are at http://buildbot.openwrt.org:8010/builders/atheros/builds/391
Sep 26 03:09:02 <builder> build #409 of at91 is complete: Failure [failed compile_4]  Build details are at http://buildbot.openwrt.org:8010/builders/at91/builds/409
Sep 26 04:04:48 <builder> build #383 of lantiq is complete: Failure [failed compile_4]  Build details are at http://buildbot.openwrt.org:8010/builders/lantiq/builds/383
Sep 26 05:54:11 <builder> build #361 of rb532 is complete: Failure [failed shell_12]  Build details are at http://buildbot.openwrt.org:8010/builders/rb532/builds/361
Sep 26 05:57:07 <builder> build #361 of ppc44x is complete: Failure [failed shell_12]  Build details are at http://buildbot.openwrt.org:8010/builders/ppc44x/builds/361
Sep 26 08:37:11 <OpenWrt-Commits> luka r38203 trunk/package/boot/uboot-imx6/Makefile * [package] uboot-imx6: alphabetize wandboard variants
Sep 26 08:37:13 <OpenWrt-Commits> luka r38204 trunk/package/boot/uboot-imx6/Makefile * [package] uboot-imx6: add support for Nitrogen6x boards
Sep 26 08:55:14 <builder> build #374 of uml is complete: Failure [failed compile_5]  Build details are at http://buildbot.openwrt.org:8010/builders/uml/builds/374
Sep 26 09:03:05 <builder> build #364 of x86 is complete: Failure [failed compile_4]  Build details are at http://buildbot.openwrt.org:8010/builders/x86/builds/364
Sep 26 09:04:48 <OpenWrt-Commits> luka r38205 trunk/package/boot/uboot-imx6/Makefile * [package] uboot-imx6: fix typo in nitrogen6dlXg
Sep 26 09:05:18 <builder> build #341 of sibyte is complete: Failure [failed shell_12]  Build details are at http://buildbot.openwrt.org:8010/builders/sibyte/builds/341
Sep 26 10:01:10 <builder> build #351 of avr32 is complete: Failure [failed shell_3 compile_4]  Build details are at http://buildbot.openwrt.org:8010/builders/avr32/builds/351
Sep 26 10:12:23 <builder> build #393 of orion is complete: Failure [failed compile_8]  Build details are at http://buildbot.openwrt.org:8010/builders/orion/builds/393
Sep 26 10:45:14 <builder> build #341 of xburst is complete: Failure [failed compile_4]  Build details are at http://buildbot.openwrt.org:8010/builders/xburst/builds/341
Sep 26 10:47:34 <builder> build #336 of ixp4xx is complete: Failure [failed compile_4]  Build details are at http://buildbot.openwrt.org:8010/builders/ixp4xx/builds/336
Sep 26 11:11:21 <builder> build #360 of ar7 is complete: Failure [failed compile_4]  Build details are at http://buildbot.openwrt.org:8010/builders/ar7/builds/360
Sep 26 11:14:10 <builder> build #297 of iop32x is complete: Failure [failed shell_12]  Build details are at http://buildbot.openwrt.org:8010/builders/iop32x/builds/297
Sep 26 11:22:42 <OpenWrt-Commits> tripolar r38206 packages/mail/dovecot/files/dovecot.init * [packages] dovecot: switch to new procd init script style
Sep 26 11:23:29 <builder> build #323 of au1000 is complete: Failure [failed compile_4]  Build details are at http://buildbot.openwrt.org:8010/builders/au1000/builds/323
Sep 26 11:24:13 <tripolar> blogic: hi, is there a way to start more programs that are handled with the new procd init script style?
Sep 26 11:24:40 <tripolar> blogic: i mean inside one init script
Sep 26 11:25:02 <blogic> sure
Sep 26 11:25:21 <blogic> you need to use the start_service function for that
Sep 26 11:25:37 <tripolar> but how? just use more procd_set_param command lines?
Sep 26 11:26:05 <tripolar> or is create more than one start_service function?
Sep 26 11:27:31 <tripolar> blogic how would i start lets say portmap inside the dovecot makefile that is also handled by procd?
Sep 26 11:28:04 <blogic> hmm
Sep 26 11:28:07 <blogic> will check in a sec
Sep 26 11:45:27 <luka> tripolar: i think you just need to have multiple procd_open_instance, procd_close_instance
Sep 26 11:45:35 <luka> look at multimedia/mjpg-streamer/files/mjpg-streamer.init
Sep 26 11:45:58 <luka> that can lanuch as many as you want daemons depending on your uci config
Sep 26 11:46:29 <blogic> luka: well
Sep 26 11:46:34 <blogic> those are instances really
Sep 26 11:46:40 <luka> yes
Sep 26 11:46:42 <blogic> as in you have a service and start 4 instances of it
Sep 26 11:46:54 <blogic> i think tripolar wants to start 4 different binaries
Sep 26 11:47:00 <luka> ah, ok
Sep 26 11:47:07 <blogic> it would work, not sure if the api was eisgned for ti though
Sep 26 11:47:18 <blogic> tripolar: do you want to start a binary 4 times
Sep 26 11:47:23 <blogic> or 4 different ones ?
Sep 26 11:53:24 <tripolar> blogic 4 different ones
Sep 26 11:54:10 <blogic> tripolar: ok
Sep 26 11:54:16 <blogic> i need to finish trolling zyxel
Sep 26 11:54:54 <tripolar> blogic: so is it working or not?
Sep 26 11:55:17 <blogic> it wil work
Sep 26 11:55:21 <blogic> i have never tried though ;)
Sep 26 11:55:27 <blogic> felix made the code
Sep 26 11:56:24 <tripolar> so just create more procd_open_instance;procd_set_param command ;procd_close_instance
Sep 26 11:56:36 <tripolar> or just more procd_set_param commands
Sep 26 12:00:29 <builder> build #296 of ep93xx is complete: Failure [failed compile_4]  Build details are at http://buildbot.openwrt.org:8010/builders/ep93xx/builds/296
Sep 26 12:04:15 <tripolar> blogic: works with multible  procd_open_instance;procd_set_param command;procd_close_instance lines
Sep 26 12:04:27 <tripolar> luka: you are right, thanks
Sep 26 12:05:00 <blogic> tripolar: yes
Sep 26 12:05:05 <blogic> that does work
Sep 26 12:09:32 <OpenWrt-Commits> tripolar r38207 packages/net/nfs-kernel-server/files/nfsd.init * [packages]: nfs-kernel-server switch to new procd init script style
Sep 26 12:09:49 <blogic> tripolar: thx !
Sep 26 12:14:39 <tripolar> blogic do you know if its possible to attach the running apps? as all of them are running in foreground this should be possible
Sep 26 12:15:12 <tripolar> attach mean - view their output in the current console like screen is doing
Sep 26 12:17:27 <blogic> tripolar: there will be a way
Sep 26 12:17:33 <blogic> i have a wippatch that will do so
Sep 26 12:26:35 <tripolar> blogic do you have a link?
Sep 26 12:26:54 <blogic> nope
Sep 26 12:26:58 <blogic> its not functional at all
Sep 26 12:27:50 <tripolar> okay, bu nice to know this will be implemented
Sep 26 12:28:46 <tripolar> blogic: whats still missing are acl lists for ubus
Sep 26 12:29:02 <tripolar> but a quick fix inbetwenn would be to set ubus - 0700
Sep 26 12:29:15 <blogic> ok
Sep 26 12:29:19 <blogic> i will tell felix about it
Sep 26 12:29:40 <tripolar> blogic: isn't he here?
Sep 26 12:30:02 <tripolar> ping nbd
Sep 26 12:30:49 <tripolar> nbd: ubus still has no acl lists but for security reasons it could be at least be set to 0700
Sep 26 12:31:31 <tripolar> so no user except root can start it
Sep 26 12:32:45 <jow_laptop> you mean the client?
Sep 26 12:34:52 <tripolar> yes
Sep 26 12:36:44 <builder> build #293 of adm5120 is complete: Failure [failed compile_4]  Build details are at http://buildbot.openwrt.org:8010/builders/adm5120/builds/293
Sep 26 12:37:49 <jow_laptop> I think you can also enforce simple access control through the filesystem permissions of /var/run/ubus.sock
Sep 26 12:38:05 <jow_laptop> this is a bit more flexible than relying on the client permissions
Sep 26 12:38:17 <jow_laptop> since someone could still e.g. use a lua script to conenct ubus
Sep 26 12:38:25 <jow_laptop> so chmodding /usr/bin/ubus is no real security
Sep 26 12:39:22 <tripolar> the best would be at least a group that the user must be a member of like ubus
Sep 26 12:39:32 <jow_laptop> yep, exactly
Sep 26 12:40:25 <tripolar> also just a little work, chmod it 770 and set the ownership to root:ubus and add the group to base-files/files/etc/group - that shoul be all
Sep 26 12:40:40 <jow_laptop> nbd: what do you think? define a "ubus" group, let ubusd create its unix socket with that group and make the permissions default to 0660 and configurable through a command line param
Sep 26 12:41:56 <tripolar> jow_laptop: it should be 770 or 550 - 660 won't work ;)
Sep 26 12:42:15 <tripolar> at least for the ubus client bin
Sep 26 12:44:25 <jow_laptop> I am talking about the socket
Sep 26 12:44:37 <jow_laptop> again there is no point in restriciting the client permission
Sep 26 12:44:50 <jow_laptop> you cna upload a custom binary to /tmp and use ubus with that
Sep 26 12:45:18 <tripolar> okay, you are right
Sep 26 12:45:22 <jow_laptop> you can use lua -lubus -e 'x=require "ubus"; x:connect(); x:call("network.interface.lan", "down", {})' etc.
Sep 26 12:51:27 <OpenWrt-Commits> tripolar r38208 packages/net/ntpd/files/ntpd.init * [packages] ntpd: switch to new procd init script style
Sep 26 13:11:56 <builder> build #275 of mpc52xx is complete: Failure [failed compile_4]  Build details are at http://buildbot.openwrt.org:8010/builders/mpc52xx/builds/275
Sep 26 13:50:37 <tripolar> blogic: do you know what is needed to get rif of this compile error on mips
Sep 26 13:50:40 <tripolar>  undefined reference to __sync_add_and_fetch_8'
Sep 26 13:52:41 <blogic> in the kernel or in userland ?
Sep 26 13:52:49 <tripolar> userland
Sep 26 13:53:48 <larsc> fix the program
Sep 26 13:53:56 <larsc> that's some x86 stuff
Sep 26 13:54:10 <blogic> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56296
Sep 26 13:54:11 <blogic> yes
Sep 26 13:55:25 <tripolar> but how can i find out which line of code pulls in this x86 stuff
Sep 26 13:55:41 <cyrusff> well search for that line that includes this function call ;)
Sep 26 13:57:58 <tripolar> found it thanks
Sep 26 14:03:04 <tripolar> blogic: this errer means what? what would i have to change to make it work
Sep 26 14:08:24 <builder> build #260 of octeon is complete: Failure [failed compile_5]  Build details are at http://buildbot.openwrt.org:8010/builders/octeon/builds/260
Sep 26 14:09:25 <cyrusff> tripolar: the error means that the program tries to do an atomic operation which is not supported on your target platform
Sep 26 14:10:23 <cyrusff> there are no atomic 64-bit operations on a 32-bit platform in general
Sep 26 14:10:38 <cyrusff> or well at least not on mips32
Sep 26 14:10:51 <cyrusff> or whatever you are building
Sep 26 15:19:12 <Devastator> dumb question: how do I sysupgrade? do I just put *-sysupgrade.bin in /tmp with scp and sysupgrade *-sysupgrade.bin?
Sep 26 15:19:41 <blogic> yes
Sep 26 15:19:56 <Devastator> thanks!
Sep 26 15:28:22 <Devastator> can't wait to play with this device :D months of work
Sep 26 17:54:11 <OpenWrt-Commits> nbd r38209 trunk/include/target.mk * build: clean up default cflags handling
Sep 26 17:54:16 <OpenWrt-Commits> nbd r38210 trunk/ (21 files in 21 dirs) * build: unify mips target cflags
Sep 26 17:54:21 <OpenWrt-Commits> nbd r38211 trunk/ (16 files in 16 dirs) * build: unify arm target cflags
Sep 26 17:54:26 <OpenWrt-Commits> nbd r38212 trunk/ (6 files in 6 dirs) * build: unify x86 target cflags
Sep 26 17:54:30 <OpenWrt-Commits> nbd r38213 trunk/ (6 files in 6 dirs) * build: unify powerpc target cflags
Sep 26 17:54:33 <OpenWrt-Commits> nbd r38214 trunk/ rules.mk scripts/metadata.pl include/target.mk * build: include the cpu type as part of the toolchain/target directory name
Sep 26 17:58:20 <jow_laptop> rebuild time...
Sep 26 17:59:01 <nbd> yep
Sep 26 17:59:18 <OpenWrt-Commits> juhosg r38215 trunk/target/linux/generic/config-3.8 * kernel/3.8: add missing config symbols
Sep 26 17:59:19 <OpenWrt-Commits> juhosg r38216 trunk/target/linux/generic/config-3.9 * kernel/3.9: add missing config symbols
Sep 26 18:02:50 <OpenWrt-Commits> juhosg r38217 trunk/target/linux/ (10 files) * kernel/3.10: add '003-11-' prefix for patches backported from 3.11
Sep 26 18:02:58 <OpenWrt-Commits> juhosg r38218 trunk/target/linux/ generic/patches-3.10/470-mtd-m25p80-add-pm25-flash-support.patch generic/patches-3.10/009-mtd_m25p80_add_support_for_esmt_f25l32pa.patch generic/patches-3.10/003-12-001-mtd-chips-Add-support-for-PMC-SPI-Flash-chips-in-m25.patch * kernel/3.10: use backported patch for PMC SPI flash support
Sep 26 18:40:25 <mazilo> I was perusing the rules.mk and am curious if the check on CONFIG_ENABLE_LOCALE line #256 makes sense.
Sep 26 18:40:27 <mazilo> ifeq ($(CONFIG_ENABLE_LOCALE),true)
Sep 26 18:40:28 <mazilo>   DISABLE_NLS:=--enable-nls
Sep 26 18:40:28 <mazilo> else
Sep 26 18:40:28 <mazilo>   DISABLE_NLS:=--disable-nls
Sep 26 18:40:28 <mazilo> endi
Sep 26 18:44:18 <Devastator> weird..
Sep 26 18:54:50 <Devastator> how can I check if my patch got accepted by the kernel? patchwork seems unchanged
Sep 26 18:56:29 <nbd> what tree was it for?
Sep 26 19:03:58 <Devastator> nbd linux-mtd
Sep 26 19:04:25 <nbd> no idea how long it usually takes for that tree
Sep 26 19:05:20 <Devastator> nbd I see that Gabor backported it, but I don't see it being mentioned in the merge
Sep 26 19:17:20 <OpenWrt-Commits> florian r38219 trunk/target/linux/rb532/image/Makefile * rb532: fix initramfs image creation (#14215)
Sep 26 19:52:05 <OpenWrt-Commits> cyrus r38220 trunk/package/ system/opkg/files/opkg-smime.conf system/opkg/Makefile system/opkg/patches/007-force_static.patch * opkg: add build variant with signature support
Sep 26 20:37:02 <mazilo> I just SVN up to r38220. Now, building OpenWRT for a Marvell Kirikwood is defaulted to ARM XSCALE. Before that, it was ARM V5TE. But, the worst is gcc 4.8.x (minimal) breaks compilation as seen here (http://pastebin.com/vbqxL62T). :(
Sep 26 21:36:11 <mazilo> Here (http://pastebin.com/nRK3q3Yz) is more information on the gcc v4.8.x (minimal) compilation.
Sep 26 21:54:10 <OpenWrt-Commits> luka r38221 trunk/include/target.mk * include/target.mk: fix spacing
Sep 26 22:17:48 * luka is build testing this patch http://pastebin.lukaperkov.net/openwrt/20130927_0001-build-fix-typo-vfp3-should-be-named-vfpv3.patch
Sep 26 22:17:59 <luka> it should fix the problem mazilo reported...
Sep 26 22:32:46 <builder> build #394 of orion is complete: Failure [failed compile_3]  Build details are at http://buildbot.openwrt.org:8010/builders/orion/builds/394
Sep 26 22:44:07 <OpenWrt-Commits> luka r38222 trunk/ target/linux/omap4/Makefile target/linux/imx6/Makefile include/target.mk target/linux/mvebu/Makefile * build: fix typo
Sep 26 22:46:57 <builder> build #384 of lantiq is complete: Failure [failed compile_4]  Build details are at http://buildbot.openwrt.org:8010/builders/lantiq/builds/384
Sep 26 22:49:20 <builder> build #362 of rb532 is complete: Failure [failed shell_12]  Build details are at http://buildbot.openwrt.org:8010/builders/rb532/builds/362
Sep 26 22:51:39 <swalker> luka: I do munge git tags for uscan (but only for 2 or 3 packages iirc)
Sep 26 22:52:19 <builder> build #362 of ppc44x is complete: Failure [failed shell_12]  Build details are at http://buildbot.openwrt.org:8010/builders/ppc44x/builds/362
Sep 26 23:07:52 <builder> build #410 of at91 is complete: Failure [failed compile_5]  Build details are at http://buildbot.openwrt.org:8010/builders/at91/builds/410
Sep 26 23:40:51 <builder> build #375 of uml is complete: Failure [failed compile_5]  Build details are at http://buildbot.openwrt.org:8010/builders/uml/builds/375
Sep 27 00:02:27 <builder> build #342 of sibyte is complete: Failure [failed shell_12]  Build details are at http://buildbot.openwrt.org:8010/builders/sibyte/builds/342
Sep 27 01:13:41 <builder> build #365 of x86 is complete: Failure [failed compile_4]  Build details are at http://buildbot.openwrt.org:8010/builders/x86/builds/365
Sep 27 01:36:05 <builder> build #352 of avr32 is complete: Failure [failed compile_4]  Build details are at http://buildbot.openwrt.org:8010/builders/avr32/builds/352
Sep 27 01:53:27 <OpenWrt-Commits> luka r38223 trunk/target/linux/ (5 files in 2 dirs) * mvebu: add 3.10 support
Sep 27 01:53:28 <OpenWrt-Commits> luka r38224 trunk/target/linux/mvebu/Makefile * mvebu: switch to 3.10
Sep 27 01:53:29 <OpenWrt-Commits> luka r38225 trunk/target/linux/ (37 files in 2 dirs) * mvebu: drop 3.8 support
Sep 27 01:53:31 <OpenWrt-Commits> luka r38226 trunk/target/linux/mvebu/Makefile * mvebu: add myself as maintainer
Sep 27 02:49:49 <builder> build #337 of ixp4xx is complete: Failure [failed compile_3]  Build details are at http://buildbot.openwrt.org:8010/builders/ixp4xx/builds/337
**** ENDING LOGGING AT Fri Sep 27 02:59:58 2013