**** BEGIN LOGGING AT Wed Feb 16 02:59:57 2011 Feb 16 03:51:50 build #84 of ubicom32 is complete: Failure [failed compile_3] Build details are at http://tksite.gotdns.org:8010/builders/ubicom32/builds/84 Feb 16 04:44:46 build #64 of adm5120 is complete: Success [build successful] Build details are at http://tksite.gotdns.org:8010/builders/adm5120/builds/64 Feb 16 10:10:08 hi Feb 16 10:10:59 is it possible to add different PKG_* VARS in Makefiles? Feb 16 11:54:36 jow * r25549 /packages/net/krb5/ (Makefile patches/002-MITKRB5-SA-2011-002.patch): [packages] krb5: MIT krb5 Security Advisory 2011-002 (CVE-2011-0281, CVE-2011-0283) Feb 16 11:56:13 is that related to the kerberos exploit they found in Ubuntu? Feb 16 11:56:21 yes Feb 16 11:58:27 jow * r25550 /packages/net/krb5/Makefile: [packages] krb5: bump pkg revision Feb 16 12:00:02 its only a dos flaw Feb 16 12:20:20 build #92 of brcm63xx is complete: Success [build successful] Build details are at http://tksite.gotdns.org:8010/builders/brcm63xx/builds/92 Feb 16 12:34:15 hi Feb 16 12:35:47 I have been given a bricked wndr3770 Feb 16 12:36:49 after havin build a transceiver board for the uart following connections from the openwrt wndr3700 web page I'm able to look at the u-boot prompt and the kernel boot messages Feb 16 12:36:55 but the rootfs fails to mount Feb 16 12:37:59 I have previously played with openwrt, and my job is to port Linux to custom arm platforms, built embedded systems and apps Feb 16 12:38:17 but flashing a .bin image is new to me Feb 16 12:38:29 37*7*0 ? Feb 16 12:38:38 oups Feb 16 12:38:39 or 3700 Feb 16 12:38:43 3700 Feb 16 12:39:04 I've seen you yesterday, haven't I :) ? Feb 16 12:39:15 just hold down reset, powercycle, keep holding until the leds start to blink eventually Feb 16 12:39:25 then tftp put the factory image to 192.168.1.1 Feb 16 12:39:35 yes you did Feb 16 12:40:00 ok so now I can use the image I built last night Feb 16 12:40:24 usualy I tftpboot an image, erase flash, program flash Feb 16 12:40:45 on those untis the bootloader can do that for you Feb 16 12:40:51 it has a tftp server builtin Feb 16 12:40:57 nice thing :) Feb 16 12:40:59 see also http://wiki.openwrt.org/toh/netgear/wndr3700 for more details Feb 16 12:41:44 that's the web page I read from top to bottom and bottom to top since yesterday :) Feb 16 12:42:58 then see the "oh I bricked my router" section Feb 16 12:43:07 it has the tftp procedure Feb 16 12:44:02 following that, I have the goal of build a special custom system Feb 16 12:44:36 the overlay will be on /dev/sda1 while the jffs2 overlay would only be used for failsafe Feb 16 13:15:11 [florian], ping Feb 16 13:16:01 tn: you can use the extroot thingy; it will automatically fall back to the jffs2 overlay if the extroot isn't present Feb 16 13:28:42 <[florian]> Wipster: pong Feb 16 13:30:54 [florian], afternoon I was just looking over .36 and I just noticed that the DSL doesn't start, its fails to register the avsar device in tn7dsl. Feb 16 13:34:09 <[florian]> Wipster: any idea why? Feb 16 13:36:54 [florian], not yet was going to see what it was returning when I get back Feb 16 13:37:51 <[florian]> Wipster: could be related to /proc entries registration again? Feb 16 13:40:04 [florian], well it falls over here device_register(&avsar) not sure if avsar needs some more detail in it, there's only a couple of errors that can return Feb 16 13:42:50 <[florian]> Wipster: allright, I could get a look at this Feb 16 13:43:00 <[florian]> Wipster: I plan on updating directly to 2.6.37 actually Feb 16 13:44:32 [florian], yeh I noticed it in the logs when I moved up to .37 and found that I missed it in .36 Feb 16 13:46:08 gotta run, back in a couple of hours Feb 16 13:48:46 <[florian]> allright Feb 16 13:51:57 kaloz * r25551 /trunk/toolchain/binutils/patches/2.20.1/ (3 files): [toolchain/binutils]: refresh patches Feb 16 14:05:34 kaloz * r25552 /trunk/toolchain/binutils/patches/2.19.1/ (4 files): [toolchain/binutils/2.19.1]: fixup the ubicom patch, refresh Feb 16 14:08:42 build #88 of at91 is complete: Success [build successful] Build details are at http://tksite.gotdns.org:8010/builders/at91/builds/88 Feb 16 14:21:45 https://forum.openwrt.org/viewtopic.php?pid=128580#p128580 <- it looks like at least the ar71xx builder still has a stale libopenssl 0.9.8 lying around Feb 16 14:24:53 I've seen builders timing out in distclean Feb 16 14:24:57 probably the case here Feb 16 15:13:21 nbd * r25553 /trunk/package/kernel/modules/block.mk: kernel: add a missing module for ahci on 2.6.35+ Feb 16 15:21:47 kaloz * r25554 /trunk/toolchain/gcc/Config.version: fixup gcc version selection Feb 16 15:25:12 kaloz * r25555 /trunk/toolchain/gcc/patches/4.3.5/ (10 files): [toolchain/gcc/4.3.5]: refresh patches Feb 16 15:26:33 kaloz * r25556 /trunk/toolchain/gcc/patches/4.3.5/ (2 files): [toolchain/gcc/4.3.5]: additional avr32 fixes Feb 16 15:43:51 build #86 of brcm47xx is complete: Success [build successful] Build details are at http://tksite.gotdns.org:8010/builders/brcm47xx/builds/86 Feb 16 16:33:11 build #88 of atheros is complete: Success [build successful] Build details are at http://tksite.gotdns.org:8010/builders/atheros/builds/88 Feb 16 16:45:33 Hello everyone Feb 16 16:45:53 i'm facing a problem on a freshly built version of openWRT (trunk) for brcm47xx arch Feb 16 16:46:52 when launching a program which need floating point it display the warning that my toolchain wasn't compile with soft float, then do it's job (i can use ssh command for instance) but at the end the program doesn't return and uses 99% of the CPU Feb 16 16:47:19 i'm building openWRT on a 32bit ubuntu 10.10. fresh install. Trunk is also completely clean Feb 16 16:48:49 for instance dropebarkey generate a key and then get stuck (it seems return is just stuck) Feb 16 16:53:01 build #75 of ps3 is complete: Failure [failed compile_3] Build details are at http://tksite.gotdns.org:8010/builders/ps3/builds/75 Feb 16 16:53:30 any idea ? Feb 16 16:54:09 clement_: how fresh? Feb 16 16:54:36 5 hours Feb 16 16:54:56 i used to built openwrt for that device before and everything was fine Feb 16 16:55:31 built from a clean tree? Feb 16 16:55:36 yes Feb 16 16:55:43 toolchain rebuilt Feb 16 16:57:07 please try this simple test program: int main(int argv, char **argv) { exit(0); } and compile it with $(CC) -lrt -o test test.c Feb 16 16:57:24 see if it hangs on your target Feb 16 16:58:15 the dmesg float emu warning is completely unrelated Feb 16 16:58:33 using gcc from the tooclhain ? Feb 16 16:58:42 its just a heads-up that the kernel has no emul and that userspace need -msoft-float Feb 16 16:58:46 yes, toolchain cc Feb 16 16:59:01 by the way, program that don't use floating point just return well (nvram, mtd..) Feb 16 16:59:13 are you sure about that? Feb 16 16:59:22 nvram uses floating point too Feb 16 16:59:44 well use... it has a double and devidies it Feb 16 16:59:48 yes i tried nvram Feb 16 17:00:41 but i don't get the warning : FPU emulator disabled, make sure your toolchainwas compiled with software floating point support (soft-float) Feb 16 17:01:48 ignore it Feb 16 17:03:30 root@OpenWrt:/tmp# ./test ./test: can't load library 'librt.so.0' Feb 16 17:05:12 as you said it's just a warning but when it appears program doesn't return at the end. Feb 16 17:06:38 xMff, what? it uses floating point AND division? :P Feb 16 17:06:42 the bane of mips Feb 16 17:15:03 i tried printf("test %f\n",34.67/576.98); and i don't get any warning. and it returns well Feb 16 17:16:32 I'd imagine if you used a hw float setup on a no-fpu system it'd just cause alot of illegal instructions Feb 16 17:18:15 even if i set sofftware FPU emulator in kernel_menuconfig i get Illegal Instructions Feb 16 17:19:00 the toolchain needs to have it set also Feb 16 17:20:13 yes that what i have done last time Feb 16 17:20:20 it's in Target Options Feb 16 17:20:33 yes i see that : Use flaoting point software by default Feb 16 17:20:46 I imagine it should be default since it's in the 'advanced' section tho Feb 16 17:30:16 zandbelt * r25557 /packages/net/ (5 files in 5 dirs): [packages] asterisk-*: allow headers for multiple versions to co-exist in staging Feb 16 17:41:51 any other idea ? Feb 16 18:00:28 [florian], ping Feb 16 18:20:56 nbd * r25558 /trunk/package/xfsprogs/ (7 files in 2 dirs): add a package for xfsprogs Feb 16 18:35:59 [florian], dunt know what I was worrying about it just needed dev_set_name and all is well Feb 16 19:53:56 <[florian]> Wipster: some upstream API change most likely Feb 16 19:58:39 build #87 of s3c24xx is complete: Failure [failed shell compile_6] Build details are at http://tksite.gotdns.org:8010/builders/s3c24xx/builds/87 Feb 16 20:03:22 [florian], yeh guess so Feb 16 20:13:32 <[florian]> Wipster: glad you found out Feb 16 20:13:40 <[florian]> Wipster: so you are running 2.6.37 on your ar7 device now? Feb 16 20:14:30 [florian], yes Feb 16 20:15:07 zandbelt * r25559 /packages/net/asterisk-1.8.x/ (3 files in 2 dirs): [packages] asterisk 1.8.x: add chan_mobile support Feb 16 20:57:49 zandbelt * r25560 /packages/net/asterisk-1.8.x/patches/300-word_alignment_arm.patch: [packages] asterisk-1.8.x: add arm/mips word alignment patch Feb 16 21:10:09 does zandbelt hang out here and have an IRC handle? Feb 16 21:37:53 zandbelt * r25561 /packages/net/asterisk-1.8.x/Makefile: [package] asterisk-1.8.x: add chan_mgcp Feb 16 21:40:08 build #77 of pxcab is complete: Failure [failed shell compile_3] Build details are at http://tksite.gotdns.org:8010/builders/pxcab/builds/77 Feb 16 22:45:30 kaloz * r25562 /trunk/toolchain/binutils/ (Config.in patches/2.20.1/700-avr32.patch): [toolchain/binutils/2.20.1]: add avr32 support Feb 17 02:03:32 build #82 of cobalt is complete: Success [build successful] Build details are at http://tksite.gotdns.org:8010/builders/cobalt/builds/82 Feb 17 02:09:35 cshore: ping Feb 17 02:09:39 * swalker wonders if anyone has packaged gogoc in favor of gw6c Feb 17 02:10:33 philipp64|laptop: asterisk < 1.8 are going to be dropped eventually iirc Feb 17 02:33:08 swalker: well, everything is dropped eventually. Feb 17 02:33:28 but asterisk 1.4 and 1.8 are considered "long-term, stable". Feb 17 02:33:49 so fixes for those two branches will continue to be maintained long after 1.6 has been retired. Feb 17 02:34:04 so weaning people onto 1.8 is doing them a favor. Feb 17 02:37:58 sorry, it's "long-term support" (LTS), not "long-term stable". See https://issues.asterisk.org/roadmap_page.php for a roadmap of EOL dates. Feb 17 02:39:31 1.4.42 for instance says "Security fixes only: 2011-04-21" and "EOL: 2012-04-21". Feb 17 02:41:01 swalker: better link here: https://wiki.asterisk.org/wiki/display/AST/Asterisk+Versions Feb 17 02:41:59 so 1.6.0 had a 2-year support life-cycle, but 1.8.x will have a 5-year support life-cycle. Feb 17 02:52:54 time to go home... Feb 17 02:57:16 philipp64|laptop: I've seen it before but zandbelt has still commented that it was his intent to replace both 1.4 and 1.6 in favor of 1.8 **** ENDING LOGGING AT Thu Feb 17 02:59:57 2011