**** BEGIN LOGGING AT Thu Jul 28 02:59:57 2011
Jul 28 03:04:41 <blaise> swalker: well, it didn't work.. lol
Jul 28 03:04:56 <Chocky> lots of love?
Jul 28 03:05:41 <blaise> swalker: it aparently didn't find any work to do.. although there's nothing special about it.. just your basic ./configure && make && make install
Jul 28 03:06:25 <blaise> make[2]: Entering directory `/home/blaise/openwrt/trunk/package/ncdu' make[2]: Nothing to be done for `compile'.
Jul 28 03:20:28 <swalker> blaise: http://pastebin.com/raw.php?i=biVnpA6t
Jul 28 03:28:46 <blaise> swalker: where did you get that?
Jul 28 03:29:36 <blaise> doesn't seem to be in trunk........
Jul 28 03:30:43 <swalker> blaise: I created it & no it isn't
Jul 28 03:34:24 <blaise> swalker: :{
Jul 28 03:34:29 <blaise> I was trying to create it...
Jul 28 03:34:30 <blaise> :G
Jul 28 03:35:17 * blaise failed
Jul 28 03:35:32 * blaise sobs profusely
**** ENDING LOGGING AT Thu Jul 28 04:47:30 2011

**** BEGIN LOGGING AT Thu Jul 28 04:42:15 2011
Jul 28 07:07:25 <builder_> build #64 of at91 is complete: Failure [failed compile_4]  Build details are at http://buildbot.openwrt.org:8010/builders/at91/builds/64
Jul 28 07:23:30 <builder_> build #62 of ubicom32 is complete: Failure [failed compile_3]  Build details are at http://buildbot.openwrt.org:8010/builders/ubicom32/builds/62
Jul 28 08:29:09 <Olipro> jow_laptop or KanjiMonster, do either of you know whether enabling GCC's Graphite will also make it get used on packages?
Jul 28 08:29:12 <Olipro> specifically, ZNC
Jul 28 10:11:58 <KanjiMonster> Olipro: I would assume so, but I never tried graphite so I can only guess. Why don't you just try if it does? ;)
Jul 28 10:44:17 <WillieNL> are the automaker and configure scripts not checking for those features and auto enable them when availible like with iconv and gettext stuff for example ?
Jul 28 10:44:21 <WillieNL> Olipro
Jul 28 10:44:57 <Olipro> KanjiMonster: sure, question is how does one know if it's being built with Graphite or not
Jul 28 10:49:58 <KanjiMonster> Olipro: find out if there's a configure option for that, find out if openwrt uses it ;) (grep is your friend)
Jul 28 10:53:12 <WillieNL> KanjiMonster: hmm about configure options. adding kernel features to a kernel menu in menuconfig, is a menu like that wishfull for being included ?
Jul 28 10:54:14 <WillieNL> personal i do think about generic stuff like acpi support and basic hw and tickrate support stuff
Jul 28 10:56:21 <CIA-89> juhosg * r27803 /trunk/target/linux/ramips/image/Makefile: ramips: fix PWH2004 image generation
Jul 28 10:56:22 <CIA-89> juhosg * r27804 /trunk/target/linux/ramips/base-files/etc/uci-defaults/network:
Jul 28 10:56:22 <CIA-89> ramips: rt305x: fix uci-defaults/network script for the RT3350 based boards
Jul 28 10:56:22 <CIA-89> This change corrects expected CPU name of Ralink RT3050, which
Jul 28 10:56:22 <CIA-89> describes itself as RT3350 (this name is ripped off chip and elevated
Jul 28 10:56:22 <CIA-89> to user space via /proc/cpuinfo.)
Jul 28 10:56:23 <CIA-89> This patch fixes wired network on DIR-300 rev B and DIR-600 rev B
Jul 28 10:56:23 <CIA-89> Signed-off-by: Slawomir Cygan <wiewior@wiewior.eu.org>
Jul 28 10:56:24 <CIA-89> juhosg * r27805 /trunk/target/linux/ramips/files/arch/mips/ralink/rt305x/ (Kconfig Makefile): ramips: rt305x: sort Kconfig/Makefile entries
Jul 28 10:56:24 <CIA-89> juhosg * r27806 /trunk/target/linux/ramips/ (2 files in 2 dirs): ramips: rt305x: rename LEDs on the DIR-300-B1
Jul 28 10:56:26 <CIA-89> juhosg * r27807 /trunk/target/linux/ramips/ (4 files in 4 dirs): ramips: rt305x: change machine id for DIR-300
Jul 28 10:56:27 <CIA-89> juhosg * r27808 /trunk/target/linux/ramips/ (7 files in 7 dirs): ramips: rt305x: add support for the DIR-600 B1,B2 boards
Jul 28 10:56:29 <CIA-89> juhosg * r27809 /trunk/target/linux/ramips/ (5 files in 4 dirs):
Jul 28 10:56:29 <CIA-89> ramips: add SPI controller driver
Jul 28 10:56:29 <CIA-89> Based on a patch by Sergiy <piratfm@gmail.com>
Jul 28 10:56:30 <CIA-89> juhosg * r27810 /trunk/target/linux/ramips/files/arch/mips/ralink/rt305x/ (devices.c devices.h):
Jul 28 10:56:30 <CIA-89> ramips: rt305x: introduce rt305x_register_spi helper
Jul 28 10:56:30 <CIA-89> Based on a patch by Sergiy <piratfm@gmail.com>
Jul 28 10:56:32 <CIA-89> juhosg * r27811 /trunk/target/linux/ramips/rt305x/config-2.6.39:
Jul 28 11:38:37 <KanjiMonster> WillieNL: I wouldn't mind it; I would put these into "Global build settings" under the "Kernel build options" (perhaps moving them into a submenu if they are getting too big)
Jul 28 11:40:32 <WillieNL> KanjiMonster: hmm ok since i think that other people will like that also.. menuconfig stuff is easyer then fixing automake tools :p
Jul 28 11:41:35 <WillieNL> and will test if it is actualy building and working .
Jul 28 11:43:01 <KanjiMonster> WillieNL: there are already a few kernel options there, so IMHO this would be the correct place for them (also what do automake tools have to do with kernel options?!)
Jul 28 11:43:32 <WillieNL> KanjiMonster: hmm nothing but that was part of my rrdtool issues :)
Jul 28 11:45:22 <WillieNL> was a long time seeking while never looked at those tools in the first place.
Jul 28 11:57:56 <CIA-89> jogo * r27814 /trunk/target/linux/ar71xx/ (10 files in 9 dirs):
Jul 28 11:57:56 <CIA-89> ar71xx: merge WZR-HP-G301NH support into WZR-HP-G300NH
Jul 28 11:57:56 <CIA-89> Now that we can use a generic name for the switch there is no need for a
Jul 28 11:57:56 <CIA-89> separate image for the WZR-HP-G301NH.
Jul 28 11:57:56 <CIA-89> Update the default network config and remove the extra image.
Jul 28 12:20:29 <CIA-89> jogo * r27815 /branches/backfire/ (8 files in 4 dirs):
Jul 28 12:20:30 <CIA-89> [backfire] swconfig: Add generic switch identifiers
Jul 28 12:20:30 <CIA-89> Backport of r27880.
Jul 28 12:20:33 <CIA-89> jogo * r27816 /branches/backfire/target/linux/ar71xx/ (3 files in 3 dirs):
Jul 28 12:20:33 <CIA-89> [backfire] ar71xx: Add generic Buffalo WZR-HP-G30XNH support
Jul 28 12:20:33 <CIA-89> Use generic switch0 to add support for both WZR-HP-G301NH and WZR-HP-G300NH
Jul 28 12:20:33 <CIA-89> with RTL8366RB.
Jul 28 13:11:41 <gzanan> Is there any devs using ralink's wifi card?
Jul 28 13:13:40 <gzanan> I wanna get my rt3070 card  works on ar7241 which is big endian.
Jul 28 13:13:56 <gzanan> But this patch not working well.
Jul 28 13:14:01 <gzanan> https://forum.openwrt.org/viewtopic.php?id=30132
Jul 28 13:15:02 <nbd> i suggest you report such issues to the appropriate lists (linux-wireless, rt2x00 list)
Jul 28 13:18:33 <nbd> it's more likely if you send out emails to those lists instead of waiting for responses on irc
Jul 28 13:24:59 <gzanan> nbd: Did you mean the list in here?http://linuxwireless.org/en/developers/MailingLists#Additional_mailing_lists
Jul 28 13:28:13 <nbd> linux-wireless@vger.kernel.org, users@rt2x00.serialmonkey.com
Jul 28 13:35:39 <gzanan> nbd: thanks/
Jul 28 13:46:57 <loswillios> ubifs for kirkwood, cool
Jul 28 14:18:13 <CIA-89> jow * r27817 /branches/backfire/package/dropbear/ (7 files in 3 dirs): [backfire] sync dropbear with trunk (#9819)
Jul 28 15:01:56 <wislerelectronic> can anyone help me to install the toolchain for dd-wrt. i wanna compile simple c code for example helloworld. but i don't understand how to setup the toolchain
Jul 28 15:02:20 <jow_laptop> this is openwrt, we have zero interest in supporting dd-wrt
Jul 28 15:02:36 <jow_laptop> besides that, dd-wrt is not really meant to be beuilt by users
Jul 28 15:02:55 <jow_laptop> *built
Jul 28 15:03:14 <wislerelectronic> ok thanks
Jul 28 15:03:31 <wislerelectronic> in #dd-wrt channel thay say i should ask here
Jul 28 15:03:46 <jow_laptop> tell them they should stop offloading support for their shitty project to us
Jul 28 15:04:12 <dirtyfreebooter> haha
Jul 28 15:04:48 <wislerelectronic> ok thanks
Jul 28 15:04:54 <wislerelectronic> sorry for my question
Jul 28 15:05:39 <nbd> i don't think you'll be getting much help on irc with that issue
Jul 28 15:05:54 <nbd> dd-wrt doesn't really encourage other people developing stuff for it
Jul 28 15:06:02 <wislerelectronic> i have some problems with the dir-300 rev B and openwrt is not workin, the lan ports will not work. and under dd-wrt it work
Jul 28 15:07:20 <wislerelectronic> it's a shit communtiy
Jul 28 15:07:26 <wislerelectronic> for dd-wrt
Jul 28 15:07:47 <nbd> heh
Jul 28 15:11:54 <jow_laptop> funny part is that his issue got fixed hours ago I think
Jul 28 15:12:46 <jow_laptop> https://dev.openwrt.org/changeset/27804
Jul 28 15:20:23 <mazilo> wislerelectronic: I do agree. I came from dd-wrt world.
Jul 28 15:20:52 <mazilo> wislerelectronic: And now, I am happy to say that I am dd-wrt free. ;)
Jul 28 15:22:44 <WillieNL> nbd: hmm the part that for some hardware like atheros stuff is a paid activation needed make me seek further for a real opensource solution ;-)
Jul 28 15:23:20 <WillieNL> nbd: but still odd they send users here to there own project :(
Jul 28 15:27:13 <nbd> WillieNL: well, the people that make dd-wrt don't hang out on irc
Jul 28 15:28:09 <WillieNL> nbd: hmm that will not surprice m anyway
Jul 28 15:29:56 <Olipro> <jow_laptop> tell them they should stop offloading support for their shitty project to us
Jul 28 15:29:59 <Olipro> ^I lolled
Jul 28 15:33:37 <WillieNL> hehehe
Jul 28 15:34:03 <WillieNL> i wanted to say something there but something did make me thinking say less is better ;-) there is enough said about it i think
Jul 28 15:51:22 * russell-- sat in a booth at OSCON yesterday, and lots of people seem to think ddwrt first for some reason.  i said, "er, no. openwrt"
Jul 28 15:52:50 <nbd> well, dd-wrt obviously caters more to normal users than openwrt
Jul 28 15:53:09 <nbd> so it's normal that it's more popular among users
Jul 28 15:53:28 <russell--> yeah
Jul 28 15:54:12 <russell--> "vastly more flexible" were words that came out of my mouth several times (wrt openwrt)
Jul 28 15:54:35 <russell--> also, i think i should be getting a commission from ubiquiti
Jul 28 15:55:14 <russell--> (as a vendor of stuff to solve people's crappy rural connectivity problems)
Jul 28 15:57:03 <russell--> turns out lots of affluent programmer types move out to the country where they don't have good infrastructure, and then suffer.
Jul 28 15:57:53 <russell--> or at least, lots of them stopped at our booth
Jul 28 16:06:36 <WillieNL> russell--: hmm this area have a pretty good infrastructure but so limited by the minds of a few ritch people and their ideas
Jul 28 16:07:11 <WillieNL> russell--: but i still have the freedom to order from any nation world wide without weird goverment import issues etc etc.. so i can not really complain and must be happy.
Jul 28 16:09:54 <WillieNL> btw the ups guy delivered my gbit switch today :)
Jul 28 16:10:05 <WillieNL> tplink  tl-sg1008d
Jul 28 16:14:53 <WillieNL> a switch heatsinks included from factory :)
Jul 28 16:14:57 <WillieNL> +with
Jul 28 16:15:42 <WillieNL> 24 eur 8 port gbit switch unmanaged -> http://lh6.ggpht.com/_5AkmcjP1eXU/S1DJ40WysRI/AAAAAAAAAWI/hRiSESqT1tk/PICT0001.JPG
Jul 28 16:16:46 <WillieNL> broadcom bcm5398 based.
Jul 28 16:51:30 <CIA-89> nbd * r27818 /trunk/package/ppp/ (25 files in 2 dirs):
Jul 28 16:51:31 <CIA-89> ppp: version bump to 2.4.5
Jul 28 16:51:31 <CIA-89> Bump to the current version of PPP.
Jul 28 16:51:31 <CIA-89> A few of the patches are either in 2.4.5 or something functionally equivalent is, so those patches were removed.
Jul 28 16:51:31 <CIA-89> 1 patch was added to accommodate pppol2pv3_addr which is referenced in a linux kernel header file, but isn't defined in the kernel header files packaged with PPP.
Jul 28 16:51:31 <CIA-89> Redux: re-instate the commenting out of the exponential back-off as requested by Felix.
Jul 28 16:51:32 <CIA-89> Signed-off-by: Philip Prindeville <philipp@redfish-solutions.com>
Jul 28 17:07:06 <philipp64|laptop> nbd: thanks!
Jul 28 17:07:55 <nbd> no problem
Jul 28 17:08:00 <nbd> i have that running on my main router now
Jul 28 17:11:45 <philipp64|laptop> excellent.
Jul 28 17:11:54 <philipp64|laptop> does your carrier send broken PADS?
Jul 28 17:12:04 <nbd> no
Jul 28 17:12:21 <nbd> but i took another look at the code and it should be ok
Jul 28 17:12:48 <philipp64|laptop> I'm going to try to get a permanent fix upstreamed to be more cross-compilation friendly, so we don't have to keep patching it.
Jul 28 17:13:03 <philipp64|laptop> at least not for that.
Jul 28 17:32:07 <philipp64|laptop> nbd: check for zero-length patches... 104, 108, 109, 350 should have been deleted...
Jul 28 17:33:34 <nbd> oh, right
Jul 28 17:33:39 <nbd> svn generates stupid patches
Jul 28 17:34:07 <philipp64|laptop> patch's -E doesn't imply an "svn delete", alas.
Jul 28 17:34:18 <philipp64|laptop> well, we could all use git.
Jul 28 17:34:36 <nbd> i'm using git
Jul 28 17:34:39 <nbd> for all of my checkous
Jul 28 17:34:44 <philipp64|laptop> oh, and 102...
Jul 28 17:34:50 <CIA-89> nbd * r27819 /trunk/package/ppp/patches/ (5 files): ppp: remove zero-length patches
Jul 28 18:08:37 <plaes> nbd: what's the policy on submitting the kernel stuff to upstream?
Jul 28 18:09:40 <nbd> plaes: what kind of kernel stuff?
Jul 28 18:10:30 <plaes> like new platform-related code
Jul 28 18:10:52 <nbd> people send it upstream when they feel that it's ready and they have time to do so
Jul 28 18:10:56 <nbd> ;)
Jul 28 18:12:26 <plaes> hmkay.. I just see that whole ar71xx is just sitting around in openwrt tree
Jul 28 18:12:50 <nbd> yes, much of it has been submitted upstream
Jul 28 18:12:53 <nbd> as ath79
Jul 28 18:13:05 <nbd> but we haven't had time to fully integrate the openwrt code with the ath79 target yet
Jul 28 18:13:42 <plaes> aha
Jul 28 18:14:47 <plaes> didn't know that it was there
Jul 28 19:05:11 <Epsylon3> hi, ive seen orion branch is now based on Linux 3.0... most of (2.6.37+) branches are on this kernel ?
Jul 28 19:54:18 <CIA-89> juhosg * r27820 /trunk/package/swconfig/ (Makefile src/uci.c): (log message trimmed)
Jul 28 19:54:18 <CIA-89> swconfig: fix backward compatibility
Jul 28 19:54:18 <CIA-89> swconfig fails to load uci configuration after the generic switch
Jul 28 19:54:18 <CIA-89> identifier changes.
Jul 28 19:54:18 <CIA-89> root@OpenWrt:/# uci show network | grep switch
Jul 28 19:54:19 <CIA-89> network.@switch[0]=switch
Jul 28 19:54:19 <CIA-89> network.@switch[0].name=eth0
Jul 28 20:07:38 <builder_> build #64 of s3c24xx is complete: Failure [failed compile_10]  Build details are at http://buildbot.openwrt.org:8010/builders/s3c24xx/builds/64
Jul 28 20:17:46 <CIA-89> nbd * r27821 /branches/backfire/package/swconfig/ (Makefile src/uci.c): swconfig: backport compatibility fix from r27820
Jul 28 20:32:52 <WillieNL> hmm how long do the buildbots take in general for finishing there builds ?
Jul 28 20:33:02 <WillieNL> +- 10 ~ 15hr if i noticed that right.
Jul 28 20:50:32 <Epsylon3> ^^ the new build log feature is really usefull :)
Jul 28 20:51:00 <Epsylon3> but that dont explain openssl build failure :
Jul 28 20:51:01 <Epsylon3> {standard input}: Assembler messages:
Jul 28 20:51:01 <Epsylon3> {standard input}:283: Error: can't resolve `.LC4' {.rodata.str1.1 section} - `.LPIC5' {*UND* section}
Jul 28 20:51:03 <Epsylon3> ^^
Jul 28 21:04:23 <Epsylon3> ok bye...
Jul 28 21:28:35 <luka12345|wiik> anyone going to ccc camp?
Jul 29 00:22:18 <builder_> build #58 of ps3 is complete: Failure [failed compile_4]  Build details are at http://buildbot.openwrt.org:8010/builders/ps3/builds/58
Jul 29 01:00:13 <oneru> Hey, who should I be bugging about a new package I've sent to the mailing list? It's been a week and as far as I can tell, no one has particularly looked at it. (Fwknopd, submitted by Jonathan Bennett)
Jul 29 02:46:08 <builder_> build #58 of ramips is complete: Failure [failed compile_4]  Build details are at http://buildbot.openwrt.org:8010/builders/ramips/builds/58
Jul 29 02:59:55 <builder_> build #58 of pxcab is complete: Failure [failed compile_4]  Build details are at http://buildbot.openwrt.org:8010/builders/pxcab/builds/58
**** ENDING LOGGING AT Fri Jul 29 02:59:56 2011