**** BEGIN LOGGING AT Mon May 25 02:59:59 2015
May 25 07:44:29 <mrkiko> The output of my diff_config script is: http://cxg.de/_a199a6.htm
May 25 07:44:54 <mrkiko> The latest working image I can find is the one from Chaos calmer, RC1, release 20 may.
May 25 07:50:42 <builder> build #9 of mpc83xx is complete: Failure [failed shell_10]  Build details are at http://buildbot.openwrt.org:8010/builders/mpc83xx/builds/9
May 25 07:52:52 <builder> build #9 of ep93xx is complete: Failure [failed shell_10]  Build details are at http://buildbot.openwrt.org:8010/builders/ep93xx/builds/9
May 25 07:55:54 <mrkiko> Secondly - is it expected that we are building wl-330n3g images (and other models) both in the "generic" and in the "rt305x" subtarget?
May 25 08:07:18 <KanjiMonster> mirko: there is no "generic" subtarget for ramips
May 25 08:09:54 <mrkiko> KanjiMonster: sorry, I was referring to the folder name
May 25 08:11:15 <KanjiMonster> mrkiko: folder name where, there is no "generic" folder in target/linux/ramips?
May 25 08:11:44 <plntyk> he probably means when downloading
May 25 08:11:53 <plntyk> https://downloads.openwrt.org/snapshots/trunk/ramips/generic/
May 25 08:14:07 <KanjiMonster> ah, okay
May 25 08:14:42 <KanjiMonster> probably some buildbot target/script treating default == generic or so, seeing as it has a different build time as the rt305x folder
May 25 08:14:47 <mrkiko> yes, plntyk; I was indicating that. thank you.
May 25 08:20:22 <mrkiko> sorry for my miss-use of some terms
May 25 08:21:25 <KanjiMonster> mirko: your problem might be that the image you are trying to build gets too large; I see you are including openvpn-openssl in it
May 25 08:24:40 <plntyk> well with the diffconfig I get an wl330n3g image - however much stuff that mrkiko wants is probably not included since its built with "m" - like filesystem - and installing these takes up too much probably
May 25 08:26:04 <KanjiMonster> mrkiko: do you use a files/ folder to add extra files?
May 25 08:29:27 <OpenWrt-Commits> jogo r45746 trunk/include/image.mk * image.mk: make image too big warnings more visible
May 25 08:35:31 <mrkiko> KanjiMonster, plntyk: no, I don't use a files/ folder. And ... my image doesn't seem too big.
May 25 08:35:53 <mrkiko> it's 3670020 nuyrd
May 25 08:36:02 <mrkiko> sorry
May 25 08:36:05 <mrkiko> 3670020 bytes
May 25 08:36:28 <mrkiko> and ... yes, I choosen various things as separate packages because I don't need them in the root fs, but still it would be confortable to have them at hand
May 25 08:36:43 <KanjiMonster> mirko: ah, so you can build an image, but it doesn't work?
May 25 08:38:02 <KanjiMonster> mirko: there's already a ticket for that, it seems the update to 3.18.14 has broken at least rt305x
May 25 08:39:24 <KanjiMonster> err
May 25 08:39:35 <KanjiMonster> mirko: sry, not you ;p
May 25 08:41:50 <KanjiMonster> mrkiko: I probably broke it. I have a wild guess what might be the issue, so I can give you a patch that might or might not help.
May 25 08:46:33 <mrkiko> KanjiMonster: :D no problems, it's funny. Unfortunately I will not be able to test it in a reasonable timeframe, but probably this evening
May 25 08:46:49 <mrkiko> KanjiMonster: for the "err" I don't know what it actuallymeans, don't worry
May 25 08:47:08 <mrkiko> KanjiMonster:However, my idea is that it's pretty easy to break this hardware specifically.
May 25 08:47:20 <KanjiMonster> mirko: that was a sound word, meaning "oops"
May 25 08:47:32 <KanjiMonster> I did it again
May 25 08:47:35 <mrkiko> ah ok :D
May 25 08:47:46 <mrkiko> :D don't worry
May 25 08:47:58 <mrkiko> here also many people read it "mirko"
May 25 08:48:13 <KanjiMonster> my fingers have a will of their own
May 25 08:48:20 <mrkiko> :) :)
May 25 08:49:12 <mrkiko> KanjiMonster: yes, I can produce the image but it will not boot; and unfortunately leds are not of big help to me. I can tell you however, that I can't see failsafe thing, so I am pretty sure it doesn't boot up right, or it doesn't arrive to that point at least.
May 25 08:49:36 <KanjiMonster> mrkiko: basically it is editing one line in the kernel, so it might be easier if I just tell you what to change, but I don't know how well complex paths translate to a screen reader, so I guess a patch would be easier for you
May 25 08:57:15 <mrkiko> no no KanjiMonster
May 25 08:57:23 <mrkiko> don't worry  - I am using a braille display
May 25 08:57:32 <mrkiko> KanjiMonster: so anything terminal is good for me
May 25 08:57:36 <KanjiMonster> ah, okay
May 25 08:57:39 <mrkiko> KanjiMonster: and I also enjoy kernel :D
May 25 08:57:53 <mrkiko> KanjiMonster: so don't be worried :D and thank you.
May 25 08:58:12 <mrkiko> I guess it will be something under arch/mips/ralink
May 25 08:58:54 <KanjiMonster> mrkiko: yes, edit Kconfig like 18, change "default y" to "default n"
May 25 08:59:20 <KanjiMonster> line 18
May 25 08:59:51 <mrkiko> config RALINK_ILL_ACC ?
May 25 09:00:08 <KanjiMonster> yes
May 25 09:00:20 <mrkiko> done
May 25 09:00:23 <mrkiko> then I issue a rebuild with
May 25 09:00:25 <mrkiko> make V=99 ?
May 25 09:00:29 <mrkiko> or should I do somethng more?
May 25 09:00:30 <KanjiMonster> yes please
May 25 09:00:34 <mrkiko> ok
May 25 09:01:09 <mrkiko> (working)
May 25 09:01:19 <mrkiko> (I mean - the PC is doing it)
May 25 09:02:09 <mrkiko> but KanjiMonster you are very very helfpul and kind to me - so you deserve special attention :D and so I'll flash my Wi-Fi Access Point (that's another wl-330n3g) with the generated image, and since it's 200 km far from here, it'll be funny :D
May 25 09:02:41 * mrkiko notes the build process didn't rebuild any module
May 25 09:04:53 <KanjiMonster> mrkiko: thanks. Well, I was the one who updated the kernel to the currently broken version, so I feel a bit obliged to fix it. So thank *you* for testing my guess - I do not have any ralink hardware to test it myself.
May 25 09:06:38 <mrkiko> No problems - you are helping me and indirectly a person who will probably (hopefully) benefit from Internet Access
May 25 09:07:41 <mrkiko> KanjiMonster: the build process believed the kernel wasn't touched and so it didn't get re-buiolt. Hmhm...
May 25 09:10:41 <KanjiMonster> mrkiko: it should have in the target/linux/install step, but since you only disabled on option, it probably only relinked everything without actually compiling much
May 25 09:11:50 <mrkiko> infact
May 25 09:18:16 <mrkiko> KanjiMonster: I'll let you know asap
May 25 09:20:35 <KanjiMonster> mrkiko: after taking a closer look at the code from RALINK_ILL_ACC, I see where it is broken, and I am more confident the change should make it boot again.
May 25 09:23:04 <mrkiko> KanjiMonster: :) I am happy about it. That lovely small AP transferred TB and TB of data I guess :D
May 25 09:23:14 <mrkiko> and - yes, I am not wrong, TB :D
May 25 09:23:18 <mrkiko> not over 3G
May 25 09:23:27 <mrkiko> so I am so happy it can boot again
May 25 09:24:17 <KanjiMonster> mrkiko: if it works, can you test one more thing? I want to rather fix it than disable it, and it might be a one liner.
May 25 09:24:45 <mrkiko> KanjiMonster: sure
May 25 09:24:55 <mrkiko> KanjiMonster: I will be tremendously slow but I'll sure do that.
May 25 09:25:17 <mrkiko> what should I test?
May 25 09:25:28 <KanjiMonster> mrkiko: no problem. today is a public holiday in germany, so I'll be around most of the day ;D
May 25 09:27:11 <mrkiko> I modified the Kconfig file in the build_dir/** , right?
May 25 09:27:28 <mrkiko> that file comes out as a result of the ramips specific patches I guess
May 25 09:28:01 <KanjiMonster> mrkiko: correct, and this time, it does not come from the ramips patches, but from an actual linux submission
May 25 09:28:19 <mrkiko> ah ok
May 25 09:29:16 <KanjiMonster> mrkiko: can you change the default in Kconfig back to y and in ill_acc.c in the same directory in line 44 replace the first REG_ILL_ACC_TYPE with ILL_INT_STATUS
May 25 09:29:39 <KanjiMonster> mrkiko: so it matches line 80 in the same file
May 25 09:30:00 <mrkiko> sure KanjiMonster
May 25 11:20:34 <builder> build #9 of mpc52xx is complete: Failure [failed shell_10]  Build details are at http://buildbot.openwrt.org:8010/builders/mpc52xx/builds/9
May 25 14:02:35 <mrkiko> KanjiMonster: are you still there?
May 25 14:04:57 <Dr-Shadow> Hi is there someone working on bcm53xx ?
May 25 14:14:55 <jbennett> is there a tentative plan for how many rc releases there will be and how long between each release?
May 25 14:19:18 <KanjiMonster> mrkiko: now I am
May 25 14:21:39 <Hauke> Dr-Shadow: I am working on bcm53xx from time to time
May 25 14:26:42 <Dr-Shadow> Hauke: I'm currently trying to build an image. I'm just wondering what would be practices about configuration. (I'm cloning from git.openwrt and then uses make defconfig / make prereq / make menuconfig -> select bcm53xx as target)
May 25 14:26:48 <Dr-Shadow> I would like to boot it from tftp
May 25 14:27:05 <Hauke> what device do your have?
May 25 14:27:13 <Dr-Shadow> tp-link archer c8
May 25 14:27:44 <Dr-Shadow> I got uart working on it. It seems there is no JTAG
May 25 14:28:47 <Hauke> you could try to select ram disk image and load that
May 25 14:29:14 <Hauke> I am mostly using a netgear r6250 where I haven't managed to get tftp boot working
May 25 14:30:26 <Hauke> Dr-Shadow: on most of the mips devices this worked: boot -tftp -elf 192.168.1.195:/brcm47xx/openwrt-brcm47xx-vmlinux-initramfs.elf
May 25 14:30:57 <Dr-Shadow> this is an ARM device
May 25 14:30:57 <Hauke> I have to eat something
May 25 14:31:00 <Dr-Shadow> BCMA soc
May 25 14:31:22 <Hauke> Dr-Shadow: they are using the same bootloader, called CFE
May 25 14:31:38 <Dr-Shadow> Yes, I could get on CFE
May 25 14:31:49 <Dr-Shadow> but ty for the command, this will help me
May 25 14:32:15 <Hauke> one problem is that tp-link provided image where they also shipp the boot loader
May 25 14:32:39 <Hauke> it could be that they somehow changed the default flashing method and it would also overwrite the bootloader
May 25 14:33:14 <Hauke> it could be that rmilecki knows more
May 25 14:33:25 <Hauke> I am leaving now for some time
May 25 14:33:40 <Dr-Shadow> Ok ty for informations
May 25 14:35:38 <rmilecki> yeah, most likely it's OK to build firmware without bootloader
May 25 14:35:45 <rmilecki> and then flash it
May 25 14:35:52 <rmilecki> but I didn't have time to try it yet
May 25 14:36:14 <rmilecki> i own ARcher C9
May 25 14:38:07 <Dr-Shadow> I don't understand what you mean
May 25 14:38:15 <Dr-Shadow> We should replace the CFE bootloader ?
May 25 14:45:47 <KanjiMonster> Dr-Shadow: all tp-link images include a CFE image, so it's not clear what happens if you try to flash an image without one, and no one tried it out yet. It should be fine, but sometimes vendors do strange stuff.
May 25 14:50:35 <mrkiko> KanjiMonster: I might be able to tell you in some minutes
May 25 14:52:55 <Dr-Shadow> I see
May 25 14:53:18 <Dr-Shadow> so it could break a bcm53xx device right ?
May 25 14:57:26 <KanjiMonster> Dr-Shadow: correct. Most likely it will flash fine. If not, it should reject the image. But if the tp-link screwed it completely up, then it might just erase CFE / write nonsense to it, hardbricking the device.
May 25 14:57:45 <KanjiMonster> So you need to decide for yourself if you are ready to take the rist ;-)
May 25 14:57:55 <Dr-Shadow> Ok, I should be carefull then since there is no JTAG on board
May 25 15:01:00 <DocMAX> anyone doing traffic mirroring to a server?
May 25 15:02:03 <rmilecki> KanjiMonster: ack
May 25 15:22:30 <Dr-Shadow> When trying to boot from network I get a "Loader is not available"
May 25 15:23:17 <Dr-Shadow> Ah elf loader is not working on my board
May 25 15:23:24 <Dr-Shadow> How can I boot an image from raw ?
May 25 15:23:43 <KanjiMonster> mrkiko: I will be AFK now for a while (preparing dinner), but you can just write me; I will see it when I return
May 25 15:24:32 <mrkiko> KanjiMonster: that's fine :D
May 25 15:33:10 <mrkiko> KanjiMonster: flashing
May 25 15:38:16 <mrkiko> KanjiMonster: it works
May 25 15:42:24 <Dr-Shadow> wut
May 25 15:42:32 <Dr-Shadow> Error: unrecognized/unsupported processor variant (0x413fc090).
May 25 15:57:34 <mrkiko> KanjiMonster: good - I can confirm you the system boots up
May 25 15:57:44 <KanjiMonster> mrkiko: awesome, thanks for testing
May 25 15:57:51 <mrkiko> Dr-Shadow: I am sorry for the situation. I don't know how to help, hoping you can make progress
May 25 15:58:12 <mrkiko> KanjiMonster: no problems :D my 200 km far AP is running again, it's incredible :D
May 25 15:58:29 <Dr-Shadow> Maybe I should distclean, I think I'm getting a weird thing on configuration
May 25 15:58:36 <mrkiko> KanjiMonster: and we are lucky, because if it needed human intervention it would have been a problem even being home :D
May 25 16:27:07 <KanjiMonster> mrkiko: if you want I can give you credit for testing, I would then add you to as a successful tester when submitting the patch; all I need is an email address and a name
May 25 16:39:44 <Dr-Shadow> I don't understand, I'm building with target=bcm53xx (brcm4708 soc)
May 25 16:39:56 <Dr-Shadow> I get this at boot : Error: unrecognized/unsupported processor variant (0x413fc090).
May 25 17:55:08 <rmilecki> Dr-Shadow: details, more details
May 25 17:55:23 <rmilecki> what did you build/install/boot/whatever
May 25 18:04:07 <OpenWrt-Commits> jogo r45747 trunk/target/linux/ramips/patches-3.18/064-MIPS-ralink-fix-clearing-the-illegal-access-interrup.patch * ramips: fix hang on boot on rt305x
May 25 18:17:03 <Dr-Shadow> rmilecki: I built openwrt for bcm53xx and I tried to tftp boot on kernel
May 25 18:17:30 <Dr-Shadow> My device is tp-link archer c8
May 25 19:52:14 <builder> build #11 of pxa is complete: Failure [failed shell_10]  Build details are at http://buildbot.openwrt.org:8010/builders/pxa/builds/11
May 25 19:52:14 <builder> build #11 of orion is complete: Failure [failed shell_10]  Build details are at http://buildbot.openwrt.org:8010/builders/orion/builds/11
May 25 19:54:30 <builder> build #11 of ppc40x is complete: Failure [failed shell_10]  Build details are at http://buildbot.openwrt.org:8010/builders/ppc40x/builds/11
May 25 20:02:10 <builder> build #11 of cobalt is complete: Failure [failed shell_10]  Build details are at http://buildbot.openwrt.org:8010/builders/cobalt/builds/11
May 25 20:02:10 <builder> build #11 of cns21xx is complete: Failure [failed shell_10]  Build details are at http://buildbot.openwrt.org:8010/builders/cns21xx/builds/11
May 25 20:40:38 <Dr-Shadow> *ugh* I think I bricked my device
May 25 20:40:43 <Dr-Shadow> serial is not working anymore
May 25 20:41:18 <zinx> i bricked serial on one of mine
May 25 20:41:26 <zinx> device still works tho
May 25 20:41:35 <Dr-Shadow> My device is not working I think
May 25 20:41:45 <zinx> :(
May 25 20:41:46 <Dr-Shadow> fully bricked
May 25 20:41:57 <zinx> how'd you do it?
May 25 20:42:44 <Dr-Shadow> stock firmware erased CFE when I tried to revert to stock
May 25 20:42:52 <zinx> O_O  that's pretty evil.
May 25 20:43:28 <zinx> if it's external nand flash you can hook up to it directly and flash (make sure you hold mcu in reset)
May 25 20:43:37 <zinx> internal, you may be able to jtag it or such
May 25 20:44:24 <Dr-Shadow> there is no jtag pinout
May 25 20:45:22 <zinx> what package is the mcu in?  qfp/soic variant or bga/dfn?
May 25 20:45:58 <Dr-Shadow> uh ?
May 25 20:46:09 <zinx> does the mcu have visible leads or no :P
May 25 20:47:17 <Dr-Shadow> http://wiki.openwrt.org/toh/tp-link/archer-c9
May 25 20:47:19 <zinx> the pinout of the mcu is often available, if you use a suitable multimeter in continuity mode you can find more convenient points to attach to
May 25 20:47:24 <Dr-Shadow> almost same hardware
May 25 20:47:54 <zinx> it's bga
May 25 20:48:11 <zinx> which is far more annoying to find pins on :/
May 25 20:49:12 <zinx> the flash chip is accessible though
May 25 20:49:22 <zinx> it's the Spansion FL128SA1F00 on that board
May 25 20:49:43 <Dr-Shadow> I open my board (this is archer c8 so...)
May 25 20:51:06 <Dr-Shadow> crap it's shielded everywhere
May 25 20:51:14 <zinx> yes
May 25 20:51:54 <Dr-Shadow> I don't know how to remove shields
May 25 20:52:29 <Dr-Shadow> are those welded ?
May 25 20:53:20 <zinx> sometimes they are
May 25 20:53:35 <zinx> sometimes they are clipped on, sometimes they are a combination of clips & welds
May 25 20:54:04 <zinx> and glue / thermal adhesives of various types
May 25 20:54:13 <zinx> never know until you find out :/
May 25 21:01:40 <Dr-Shadow> clipped
May 25 21:01:51 <Dr-Shadow> puf it's easy to remove shields on this one, I'm lucky
May 25 21:06:56 <Dr-Shadow> So Spansion FL128SA1F00 is the flash chip ?
May 25 21:09:06 <zinx> Dr-Shadow: on the screenshot you posted yes
May 25 21:09:18 <zinx> erh, not screenshot, pictures, whatever
May 25 21:10:00 <zinx> doesn't mean your Archer-C8 is the same though
May 25 21:10:08 <Dr-Shadow> I got the same
May 25 21:10:13 <zinx> and i didn't immediately find images of the C8 so i gave up :P
May 25 21:10:38 <Dr-Shadow> The archer c8 as almost same board, different chips and stuff
May 25 21:10:41 <Dr-Shadow> has*
May 25 21:11:08 <Dr-Shadow> so I should programm the flash chip manually ?
May 25 21:11:33 <zinx> anyway, careful attachment of wires (using clip-on adapter with spring loaded pins for the chip would be easiest), and you can flash it.  you'll have to figure out how to keep the mcu from talking to it at the same time - maybe as simple as shorting the reset button
May 25 21:11:59 <zinx> you'll need something capable of flashing raw nand of course
May 25 21:12:06 <Dr-Shadow> My pirate bus should be able to do that
May 25 21:12:11 <zinx> aye
May 25 21:12:31 <mrkiko> congratulations guys - you're amazing
May 25 21:14:22 <Dr-Shadow> why ?
May 25 21:16:59 <OpenWrt-Commits> nbd r45748 trunk/package/network/config/netifd/Makefile * netifd: bump to current HEAD
May 25 21:17:05 <OpenWrt-Commits> nbd r45749 trunk/target/linux/mpc85xx/files/arch/powerpc/boot/dts/tl-wdr4900-v1.dts * mpc85xx: TL-WDR4900: Fix port 6 being shown as up (10MBit/half) in LUCI/swconfig
May 25 21:17:11 <OpenWrt-Commits> nbd r45750 trunk/package/system/ubus/Makefile
May 25 21:17:12 <OpenWrt-Commits> ubus: update to the latest version, switch to git.openwrt.org, fixes a lua binding memory leak
May 25 21:17:33 <DonkeyHotei> is 15.05 branched yet?
May 25 21:18:05 <nbd> no
May 25 21:21:22 <Dr-Shadow> my probes are not designed for that. I will have to grab something else for probing
May 25 21:21:25 <mrkiko> Dr-Shadow: because doing these things isn't something you do if you don't have the ... how to say, right attitude
May 25 21:21:52 <Dr-Shadow> I don't understand
May 25 21:22:24 <mrkiko> oh, I am too confused due to the needing of sleep to explain properly :D sorry Dr-Shadow but... go ahead with this excellent work
May 25 21:22:53 <Dr-Shadow> this is not excellent, I bricked my device ! *nods*
May 25 21:23:53 <mrkiko> Oh - I didn't notice, but I think you'll be able to recover it. Or - best, I hope so. Tp-link devices aren't easy to manage
May 25 21:24:06 <mrkiko> at least - that's my impression
May 25 21:24:12 <Dr-Shadow> I agree
May 25 21:24:23 <Dr-Shadow> I lost the CFE when I tried to restore the stock firmware
May 25 21:25:08 <mrkiko> So the only solution would be to have another exact same device?
May 25 21:25:31 <mrkiko> Hoping you didn't overwrite the MAC-data
May 25 21:26:56 <mrkiko> sorry guys
May 25 21:26:58 <mrkiko> going to sleep
May 25 21:27:12 <mrkiko> Dr-Shadow: hoping the best
May 25 21:27:13 <mrkiko> bye
May 25 21:27:30 <mrkiko> (please write me in PM if you see I don't answer in some time; sorry)
May 25 21:27:51 <Dr-Shadow> ty mrkiko, see ya
May 25 21:32:57 <builder> build #11 of ipq806x is complete: Failure [failed compile_4]  Build details are at http://buildbot.openwrt.org:8010/builders/ipq806x/builds/11
May 25 22:01:34 <OpenWrt-Commits> nbd r45751 trunk/package/system/fstools/Makefile
May 25 22:01:34 <OpenWrt-Commits> fstools: update to the latest version, makes filesystem initialization state tracking more reliable (#19564)
May 25 22:01:55 <mirko> KanjiMonster: kinda feel flattered :P
May 25 22:51:49 <DocMAX> jow_laptop?
May 25 22:52:14 <builder> build #10 of avr32 is complete: Failure [failed shell_10]  Build details are at http://buildbot.openwrt.org:8010/builders/avr32/builds/10
May 25 22:56:23 <DocMAX> is anybody doing port mirroring? (iptables TEE)
May 25 22:59:38 <russell--> cyrusff: would you expect henet dynamic tunnel to work in a multiwan environment? /me having trouble getting dynamic tunnel working, ifstatus is whining about subsystem interface code NO_DEVICE
May 25 23:00:33 <OpenWrt-Commits> nbd r45752 trunk/toolchain/uClibc/patches-0.9.33.2/012-elf-Add-STT_GNU_IFUNC-from-glibc.patch * uClibc: elf: Add STT_GNU_IFUNC from glibc
May 25 23:00:43 <OpenWrt-Commits> nbd r45753 trunk/target/linux/kirkwood/config-3.18 * kirkwood: disable the bogus CONFIG_IP_ADVANCED_ROUTER override (#19722)
May 25 23:12:29 <OpenWrt-Commits> nbd r45754 trunk/toolchain/ musl/Config.version musl/patches/001-git-2015-05-25.patch musl/patches/001-git-2015-03-28.patch musl/common.mk * musl: update to version 1.1.9
May 25 23:37:14 <russell--> hmm. part of the problem is that i didn't have 6in4 installed, lol
May 25 23:55:14 <DonkeyHotei> russell--: how did you figure out they're using that?
May 25 23:55:25 <DonkeyHotei> nvm, misread
May 25 23:56:17 <DonkeyHotei> but you should definitely investigate the ipv6 the actiontec was giving you
May 26 01:22:19 <russell--> DonkeyHotei: it wasn't giving it to me, it got it for itself afaict
May 26 01:22:59 <russell--> this is on a mikrotik rb493g, so the update process is a bit tedious
May 26 01:46:37 <jbennett> Well, that's a problem. Somebody that has commit access to github/openwrt/packages.git decided to "fix" one of the packages I maintain.
May 26 02:10:44 <DonkeyHotei> jbennett: well, you can fix it back, right?
May 26 02:11:41 <jbennett> I would like the two offending commits reverted, if possible. But yeah, I'll fix it
May 26 02:27:57 * jbennett officially needs a faster processor
May 26 02:33:08 <DonkeyHotei> at some point you can build openwrt ON openwrt
May 26 02:34:27 <jbennett> DonkeyHotei: I've built a kernel on a raspi. That was an exercise in patience.
May 26 02:47:37 <jbennett> DonkeyHotei: or whoever else knows, For a package that uses autotools, is it still preferred to patch configure.ac and use "PKG_FIXUP:=autoreconf"?
May 26 02:49:35 <DonkeyHotei> i've seen that in a few pkgs, no idea whether it's preferred
**** ENDING LOGGING AT Tue May 26 02:59:58 2015