**** BEGIN LOGGING AT Wed Feb 04 02:59:58 2015
Feb 04 03:27:03 <builder> build #326 of realview is complete: Success [build successful]  Build details are at http://buildbot.openwrt.org:8010/builders/realview/builds/326
Feb 04 05:37:47 <builder> build #740 of au1000 is complete: Success [build successful]  Build details are at http://buildbot.openwrt.org:8010/builders/au1000/builds/740
Feb 04 06:12:24 <OpenWrt-Commits> blogic r44252 trunk/package/kernel/mac80211/patches/330-ath5k-fix-spontaneus-AR5312-freezes.patch * ath5k: fix spontaneus AR5312 freezes
Feb 04 06:12:39 <OpenWrt-Commits> blogic r44253 trunk/package/base-files/files/lib/functions.sh * base-files: default_postinst() fix variable colision
Feb 04 06:12:45 <OpenWrt-Commits> blogic r44254 trunk/target/linux/ar71xx/base-files/etc/uci-defaults/01_leds * at71xx: TP-LINK Archer: add 5GHz led entry
Feb 04 06:12:53 <OpenWrt-Commits> blogic r44255 trunk/target/ (9 files in 7 dirs) * ar71xx: add support for the TP-LINK TL-WR941ND v5
Feb 04 06:13:29 <OpenWrt-Commits> blogic r44256 trunk/package/kernel/linux/modules/usb.mk * linux/modules: add support for Asix ax88179 USB-Gigabit Ethernet adapters
Feb 04 06:13:34 <OpenWrt-Commits> blogic r44257 trunk/package/ kernel/mt76/patches/0001-mt7602-remove-vht-capabilities.patch kernel/mt76/patches * ralink: remove VHT capabilities when not using 802.11ac
Feb 04 07:01:51 <builder> build #284 of omap is complete: Failure [failed compile_4]  Build details are at http://buildbot.openwrt.org:8010/builders/omap/builds/284
Feb 04 09:08:56 <mripard_> Kaloz: ping?
Feb 04 10:19:17 <Kaloz> mripard_: icmp echo reply
Feb 04 10:25:33 <mripard_> :)
Feb 04 10:25:46 <mripard_> I'm working on the mvebu patches again
Feb 04 10:26:32 <mripard_> what exactly do you mean by parsing the profiles?
Feb 04 10:27:19 <mripard_> as in "use grep -r Profile/ target/linux/mvebu/profiles", or do you have something else in mind?
Feb 04 11:00:02 <rmax> I wanted to point the ramips people here to www.aliexpress.com/item/x/32272481760.html
Feb 04 11:00:48 <rmax> I just stumbled over it and saw it comes with openwrt preinstalled, but there does not seem to be support for it in upstream openwrt yet.
Feb 04 11:01:49 <rmax> The case looks similar to some Buffalo devices, but I haven't found one that comes with an SD card slot like this.
Feb 04 11:14:24 <Kaloz> mripard_: let me find a changeset to show you what I want to mimic
Feb 04 11:15:19 <Kaloz> mripard_: msg
Feb 04 11:27:05 <karlp> rmax: looks like a nice device.
Feb 04 11:30:17 <rmax> karlp: yes, indeed.
Feb 04 11:31:05 <karlp> I've got fibre at home now, no longer need the dsl portion of the ISP provided router :)
Feb 04 11:31:18 <karlp> might actually get openwrt for home, not just for work :)
Feb 04 11:37:47 <rmax> Not sure what they mean by TTL in the feature list and in the board diagram. Could be either TTL-Level UART or GPIO.
Feb 04 11:38:50 <karlp> uart I would presume
Feb 04 11:56:50 <Kaloz> rmax: looks like a buffalo in white
Feb 04 11:58:14 <rmax> Kaloz: Yes, but I haven't found a buffalo with SD card slot and/or similar connector locations.
Feb 04 11:58:58 <Kaloz> rmax: sure, I just say they copied the enclosure :)
Feb 04 12:01:52 <rmax> Maybe the plastic factory just reused the mold they had already laying around for Buffalo.
Feb 04 12:12:46 <builder> build #510 of mpc85xx is complete: Failure [failed shell_14]  Build details are at http://buildbot.openwrt.org:8010/builders/mpc85xx/builds/510
Feb 04 15:16:03 <builder> build #874 of orion is complete: Failure [failed compile_1]  Build details are at http://buildbot.openwrt.org:8010/builders/orion/builds/874
Feb 04 15:35:59 <builder> build #59 of ramips.mt7621 is complete: Failure [failed compile_4]  Build details are at http://buildbot.openwrt.org:8010/builders/ramips.mt7621/builds/59
Feb 04 15:51:22 <builder> build #327 of pxa is complete: Failure [failed shell_10]  Build details are at http://buildbot.openwrt.org:8010/builders/pxa/builds/327
Feb 04 20:33:10 <builder> build #210 of brcm63xx.smp is complete: Success [build successful]  Build details are at http://buildbot.openwrt.org:8010/builders/brcm63xx.smp/builds/210
Feb 04 21:27:45 <builder> build #307 of sunxi is complete: Success [build successful]  Build details are at http://buildbot.openwrt.org:8010/builders/sunxi/builds/307
Feb 04 22:24:34 <Zero_Chaos> oh man, I'm home
Feb 04 22:24:41 <Zero_Chaos> PKG_VERSION:=1.2_rc1 <-- is this valid in openwrt? does it understand alpha/beta/rc order?
Feb 04 22:25:16 <swalker> "it"? opkg?
Feb 04 22:26:11 <Zero_Chaos> I'm fixing up some oldpackages Makefiles. so "it" is buildroot
Feb 04 22:26:22 <Zero_Chaos> but yeah, I guess opkg has to understand as well
Feb 04 22:39:52 <jow_laptop> Zero_Chaos: yes, but avoid underscores
Feb 04 22:41:18 <jow_laptop> Zero_Chaos: and the answer to your question is yes:
Feb 04 22:41:19 <jow_laptop> root@jj:~# opkg compare-versions 1.2_rc1 '>>' 1.2 && echo yes || echo no
Feb 04 22:41:19 <jow_laptop> no
Feb 04 22:41:26 <jow_laptop> root@jj:~# opkg compare-versions 1.2_rc1 '<<' 1.2 && echo yes || echo no
Feb 04 22:41:26 <jow_laptop> yes
Feb 04 22:49:07 <Zero_Chaos> jow_laptop: so upstream calls the version 1.2 rc1, if you don't like 1.2_rc1, what should I call it? (we use underscores in gentoo)
Feb 04 22:49:35 <Zero_Chaos> jow_laptop: the source tarball is 1.2_rc1.tar.xz
Feb 04 22:51:05 <Zero_Chaos> jow_laptop: sorry, it's 1.2-rc1
Feb 04 22:51:20 <Zero_Chaos> jow_laptop: you want me to use a dash like that? is that better than underscore, or what is preferred?
Feb 04 22:52:07 <jow_laptop> yes, dash is better
Feb 04 22:52:36 <Zero_Chaos> jow_laptop: okay, works for me
Feb 04 22:53:58 <Zero_Chaos> DEPENDS:=+libpthread +libopenssl +libpcap
Feb 04 22:54:23 <Zero_Chaos> what up with "+dep" is that just the syntax or does "DEPENDS:=dep" something else?
Feb 04 22:55:08 <jow_laptop> dep means "hide until dep is enabled", "+dep" means "select this dep"
Feb 04 22:55:18 <Zero_Chaos> jow_laptop: okay, thanks
Feb 04 22:56:34 <Zero_Chaos> now for the tough one, I know what the deps are in gentoo, but how do I find the openwrt names for that? Like if I know I need libnl 3.x (no 1.x) how do I deal with that?
Feb 04 22:59:27 <jow_laptop> grep -r BuildPackage,libnl package/
Feb 04 23:01:21 <Zero_Chaos> jow_laptop: looks like in this case it doesn't matter :-)
Feb 04 23:01:35 <jow_laptop> yeah, irrc we only package 3.x
Feb 04 23:01:43 <Zero_Chaos> jow_laptop: is there a way to do "libnl or libnl-tiny"?
Feb 04 23:01:43 <jow_laptop> all core stuff uses libnl-tiny
Feb 04 23:01:49 <jow_laptop> no
Feb 04 23:01:53 <jow_laptop> you need to decide
Feb 04 23:02:10 <_trine> DEPENDS:=+libpthread +libopenssl +libpcap +libnl-tiny
Feb 04 23:02:17 <Zero_Chaos> jow_laptop: what if a user wants to install libnl (not -tiny) and I only dep on +libnl?
Feb 04 23:02:27 <jow_laptop> if it works with libnl-tiny then there's no reason to support libnl
Feb 04 23:02:34 <jow_laptop> since libnl-tiny is always part of the base image
Feb 04 23:02:38 <jow_laptop> netifd, procd etc. require it
Feb 04 23:02:41 <_trine> http://paste.debian.net/144011/
Feb 04 23:02:44 <jow_laptop> wpad
Feb 04 23:03:09 <Zero_Chaos> jow_laptop: so basically, if a user wants libnl, they will pretty much always get libnl-tiny no matter what?
Feb 04 23:03:15 <jow_laptop> yes
Feb 04 23:03:41 <Zero_Chaos> jow_laptop: okay
Feb 04 23:04:16 <Zero_Chaos> jow_laptop: any clue why -Wall was forced in CFLAGS? that's not a thing right? Like I'm not supposed to be doing that....
Feb 04 23:04:29 <jow_laptop> hm?
Feb 04 23:04:51 <Zero_Chaos> jow_laptop: in aircrack-ng, -Wall was force added to CFLAGS for some unknown/insane reason.
Feb 04 23:04:58 <Zero_Chaos> jow_laptop: I assume it's safe to not do that...
Feb 04 23:05:10 <jow_laptop> -Wall is fine, -Werror would be suicidal
Feb 04 23:05:32 <jow_laptop> but if the codebase is full of warnings than -Wall makes no sense either
Feb 04 23:05:36 <Zero_Chaos> jow_laptop: I don't typically force CFLAGS for fun, -Wall seems like it's no reason to force add
Feb 04 23:05:49 <jow_laptop> yeah, try to remove any overrides
Feb 04 23:05:54 <Zero_Chaos> jow_laptop: for sure
Feb 04 23:05:54 <jow_laptop> expect those actually needed
Feb 04 23:06:01 <jow_laptop> *except
Feb 04 23:06:20 <Zero_Chaos> jow_laptop: yeah, gentoo dev, so pretty familiar with "needed" versus "that has no purpose"
Feb 04 23:07:48 <Zero_Chaos> jow_laptop: the original Makefile doesn't package docs or man pages, is that desirable?
Feb 04 23:08:11 <jow_laptop> yes
Feb 04 23:08:24 <jow_laptop> remember 4MB targets
Feb 04 23:08:39 <jow_laptop> you don't want man pages or a 123K libnl when a 13K one is available :)
Feb 04 23:08:50 <Zero_Chaos> jow_laptop: I'm used to users have a bit more options and me not choosing what they want or not :-)
Feb 04 23:09:10 <jow_laptop> well, choose with size in mind
Feb 04 23:09:13 <jow_laptop> smaller is better
Feb 04 23:09:20 <jow_laptop> noone is going to read man pages on his router
Feb 04 23:09:31 <Zero_Chaos> fighting....so hard...not to make....size joke...
Feb 04 23:09:36 <Zero_Chaos> PKG_SOURCE_URL:=http://download.aircrack-ng.org/ \ http://archive.aircrack-ng.org/aircrack-ng/$(PKG_VERSION)/
Feb 04 23:09:54 <Zero_Chaos> wtf is that? I assume I can drop the first link which seems pointless and unneeded?
Feb 04 23:10:53 <swalker> the second doesn't have the 1.2rc...
Feb 04 23:11:24 <Zero_Chaos> swalker: it's in PKG_VERSION, the first one doesn't even show a file
Feb 04 23:12:14 <jow_laptop> well the website points to http://download.aircrack-ng.org/aircrack-ng-1.2-rc1.tar.gz
Feb 04 23:12:47 <Zero_Chaos> jow_laptop: I more meant, do I really need two things in there, or just the right link?
Feb 04 23:12:48 <swalker> http://download.aircrack-ng.org/ - PKG_SOURCE_URL, aircrack-ng-1.2-rc1.tar.gz - PKG_(NAME|VERSION)
Feb 04 23:12:54 <_trine> and it does not work but git mirror does
Feb 04 23:13:11 <jow_laptop> Zero_Chaos: one is enough. Maybe they move away older versions to the archive url
Feb 04 23:13:24 <jow_laptop> Zero_Chaos: and therfore the 2nd url was added in the past
Feb 04 23:14:08 <swalker> several packages have multiple source urls for "different" upstreams
Feb 04 23:14:18 <Zero_Chaos> jow_laptop: heh, maybe, but the first url isn't even complete, so I don't know what was going on there.
Feb 04 23:14:30 <Zero_Chaos> PKG_RELEASE start at 0 or 1?
Feb 04 23:15:14 <swalker> PKG_SOURCE_URL + PKG_NAME = file being fetched
Feb 04 23:15:42 <swalker> should be 1
Feb 04 23:15:57 <Zero_Chaos> I haven't tested this yet, but does this look generally sane? https://bpaste.net/show/15eb447f7309
Feb 04 23:17:13 <Zero_Chaos> deps are also not quite right yet, but it should actually build
Feb 04 23:17:14 <swalker> likely will break if upstream moves away the current version and you go removing the archive url
Feb 04 23:17:44 <Zero_Chaos> swalker: upstream typically keeps them in place actually (I'm upstream)
Feb 04 23:19:44 <jow_laptop> Zero_Chaos: remove $(PKG_SOURCE) from the donwload url
Feb 04 23:19:57 <swalker> how big is the package going to be given you're packaging all of the binaries?
Feb 04 23:20:21 <_trine> too big for me
Feb 04 23:20:25 <Zero_Chaos> swalker: as big as it needs to be to have all the features?
Feb 04 23:20:36 <jow_laptop> the rest looks like it could build
Feb 04 23:20:51 <Zero_Chaos> swalker: I was considering dropping the "unstable" stuff. That was there already but not sure if people really care.
Feb 04 23:21:35 <swalker> Zero_Chaos: well, that's your decision
Feb 04 23:22:06 <Zero_Chaos> is ethtool not packaged? I don't see it in here.
Feb 04 23:22:12 <jow_laptop> I'd say bring it to compile at all first, later one can think about maybe splitting it
Feb 04 23:22:22 <swalker> ethtool is packaged
Feb 04 23:23:02 <Zero_Chaos> swalker: in the standard feeds?
Feb 04 23:23:27 <swalker> locate ethtool | grep package
Feb 04 23:23:46 <Zero_Chaos> swalker: I'm a moron, I was in the wrong folder :-)
Feb 04 23:25:02 <Zero_Chaos> is PCRE stuff common, or typically left out?
Feb 04 23:26:59 <jow_laptop> whats the relation to aircrack?
Feb 04 23:27:06 <jow_laptop> (I don't know it...)
Feb 04 23:27:51 <jow_laptop> ah regexp matching for ssids
Feb 04 23:27:57 <jow_laptop> leave it out for now
Feb 04 23:28:18 <swalker> how much of a pita is it going to be to remove it :)
Feb 04 23:28:19 <Zero_Chaos> jow_laptop: I figure if a lot of other things require it, I'd use it, but if not, it's not needed
Feb 04 23:28:27 <Zero_Chaos> swalker: it's entirely optional
Feb 04 23:28:58 <_trine> by the way reaver has not been able to work in openwrt for ages now
Feb 04 23:29:12 <Zero_Chaos> _trine: it's on my list. as is mdk3
Feb 04 23:29:23 <_trine> mdk3 works
Feb 04 23:29:26 <swalker> builds but broken?
Feb 04 23:29:27 <Zero_Chaos> _trine: but first thing is first :-)
Feb 04 23:29:33 <Zero_Chaos> _trine: mdk3 doesn't even build over here...
Feb 04 23:29:46 <Zero_Chaos> _trine: and it's in oldpackages and unmaintained
Feb 04 23:30:29 <Zero_Chaos> is line length a critical style issue here? should I be trimming to <81 char or kinda whatever?
Feb 04 23:30:44 <jow_laptop> not critical
Feb 04 23:31:30 <Zero_Chaos> okay, where do I drop my new makefile for testing now?
Feb 04 23:31:54 <Zero_Chaos> feeds/packages?
Feb 04 23:32:17 <jow_laptop> mkdir -p package/aircrack-ng
Feb 04 23:32:26 <jow_laptop> put it into package/aircrack-ng/Makefile
Feb 04 23:32:37 <Zero_Chaos> jow_laptop: straight in package? is there where I'd send the PR for?
Feb 04 23:33:42 <jow_laptop> for a PR it would need to go into feeds/packages/net/aircrack-ng/Makefile
Feb 04 23:34:10 <jow_laptop> I just usually throw my devel stuff into package/ as it is immediately picked up then, without the need for a feed update and install
Feb 04 23:34:31 <Zero_Chaos> jow_laptop: should just need the install -a part though, right?
Feb 04 23:35:21 <jow_laptop> well you will need an update the first time as well sence you add a new package to the feed
Feb 04 23:35:29 <jow_laptop> and openwrt needs to pickup its metadata
Feb 04 23:35:38 <jow_laptop> so once ./scripts/feeds update packages
Feb 04 23:35:44 <Zero_Chaos> jow_laptop: okay, your way is better then :-)
Feb 04 23:35:54 <jow_laptop> and once ./scripts/feeds install aircrack-ng
Feb 04 23:36:05 <jow_laptop> afterwards it is usually neough to edit the Makefile
Feb 04 23:37:08 <Zero_Chaos> well, I missed the talk I wanted to go to, but it's building now :-)
Feb 04 23:40:10 <Zero_Chaos> is "make -j" typically supported or a bad idea?
Feb 04 23:40:21 <Zero_Chaos> where -j can be -j or anything higher than -j1
Feb 04 23:41:17 <_trine> typically 1 more than the number of cores
Feb 04 23:41:57 <Zero_Chaos> I have 8 cores but -j8 reliably fails for me, and typically with error messages far too buried for my liking
Feb 04 23:42:22 <_trine> to find error you need to build without -j
Feb 04 23:42:42 <_trine> make V=s
Feb 04 23:43:09 <karlp> ack '\*\*\
Feb 04 23:43:13 <karlp> ' logs
Feb 04 23:43:15 <Zero_Chaos> okay, so by and large -j8 should work, got it
Feb 04 23:43:16 <karlp> with less line breaks :)
Feb 04 23:51:32 <Zero_Chaos> on my host, the Makefile automatically detects libnl3 and adds "-DCONFIG_LIBNL30 -DCONFIG_LIBNL -I/usr/include/libnl3" to the compile strings
Feb 04 23:51:50 <Zero_Chaos> but it doesn't work on buildroot.  How do I add -I/usr/include/libnl3 properly?
Feb 04 23:52:05 <Zero_Chaos> pkg-config does it in the makefile, maybe that is my issue?
Feb 04 23:52:09 <_trine> mdk3 just compiled here
Feb 04 23:53:08 <_trine> and so did aircrack 1.2-rc1
Feb 04 23:53:29 <swalker> you don't want *host* paths to begin with
Feb 04 23:53:43 <Zero_Chaos> swalker: yes, I realize that :-)
Feb 04 23:54:00 <Zero_Chaos> _trine: then why on earth am I trying to be maintainer if you are so much better at this? :-D
Feb 04 23:54:52 <karlp> hrm, I want somethign like that ramips device rmax posted earlier, but with two usb ports.
Feb 04 23:55:16 <_trine> I am not better
Feb 04 23:55:52 <Zero_Chaos> _trine: both are working for you, both are not working for me. I'd say that gives you at least a leg to stand on to say you are better at this than I am ;-)
Feb 04 23:57:18 <_trine> I am 70 next week so there is no guarantee of of any continuity :)
Feb 04 23:57:59 <Zero_Chaos> _trine: pssh, I'm 31 but that doesn't help if I get hit by a truck. We could all die, hell, I haven't eaten all day, if I don't have dinner I may just waste away
Feb 05 00:00:05 <Zero_Chaos> bahahahahaha
Feb 05 00:00:11 <Zero_Chaos> failure for lack of a properly place \
Feb 05 00:00:59 <_trine> the only problem I had with compiling aircrack was that my makefile could not find the tar ball so I just downloaded it to /dl but later I found I could do the same using the git mirror
Feb 05 00:01:35 <_trine> when it was beta3 it worked fine
Feb 05 00:02:29 <_trine> but 1.2-rc1 was not in the same place on the aircrack site
Feb 05 00:02:51 <_trine> as far as I recall
Feb 05 00:02:56 <Zero_Chaos> okay, here is the bad build log: http://pastebin.com/Mzqr1JT5
Feb 05 00:05:12 <Zero_Chaos> and here is a good one, same config: http://pastebin.com/4B8P7k48
Feb 05 00:05:30 <Zero_Chaos> looks like "make libnl=true" isn't actually getting the makefile to drop stuff in like it's supposed to
Feb 05 00:05:47 <Zero_Chaos> missing "-DCONFIG_LIBNL30 -DCONFIG_LIBNL -I/usr/include/libnl3"
Feb 05 00:07:33 <Zero_Chaos> I'm guessing this chunk of the upstream Makefile is bad: http://pastebin.com/QCszBhF2
Feb 05 00:07:43 <Zero_Chaos> anyone have an idea how to properly call pkg-config in openwrt?
Feb 05 00:10:03 <swalker> what's the libnl*.pc look like in the staging_dir?
Feb 05 00:11:41 <Zero_Chaos> swalker: good idea, I think the issue is that libnl-tiny calls itself libnl-tiny, and aircrack-ng isn't build for that.
Feb 05 00:12:32 <Zero_Chaos> swalker: yup, aircrack-ng only checks libnl-tiny for libnl1
Feb 05 00:13:53 <Zero_Chaos> but changing +libnl-tiny to +libnl didn't fix it
Feb 05 00:14:04 <Zero_Chaos> looks like the Makefile still isn't running pkg-config correctly
Feb 05 00:14:56 <Zero_Chaos> this looks to be the offending line in the upstream Makefile:
Feb 05 00:14:58 <Zero_Chaos> NL3xFOUND := $(shell $(PKG_CONFIG) --atleast-version=3.2 libnl-3.0 && echo Y)
Feb 05 00:15:14 <Zero_Chaos> is that even theoretically supposed to work? it runs pkg-config on the shell...
Feb 05 00:15:54 <Zero_Chaos> I need some food, I'll be back when maybe I can think straight :-)
Feb 05 00:16:02 <Zero_Chaos> thanks for all the help everyone
Feb 05 00:17:10 <_trine> this makefile works except it does not get the code so you need to download the tarball and put it in /dl
Feb 05 00:17:14 <_trine> http://paste.debian.net/144011/
Feb 05 00:18:00 <_trine> to make it work please put the code in the right place on the aircrack-ng site
Feb 05 00:34:01 <karlp> heh, these devices look cute, http://www.vonets.com/ProductViews.asp?D_ID=33# but they provide a custom linux 2.6 tree. yech
Feb 05 01:22:53 <DonkeyHotei> karlp: i'm sure support could be merged
Feb 05 01:26:40 <karlp> yeah,
Feb 05 01:27:01 <karlp> about to pull the trigger on this http://www.aliexpress.com/store/product/DIY-SUPER-OPENWRT-Kernel-WAN-300Mbps-Wi-Fi-Wireless-Router-WiFi-Repeater-Roteador-Support-USB-3G/128677_32272246018.html
Feb 05 01:27:04 <Zero_Chaos> _trine: you aren't adding libnl=true, so the resulting code won't work right unless this is 2010
Feb 05 01:27:18 <karlp> the vonet things look cute, but not what I actually need right now
Feb 05 01:28:00 <swalker> Zero_Chaos: remove the CFLAGS override from MAKE_FLAGS
Feb 05 01:29:17 <DonkeyHotei> karlp: is that different from http://www.aliexpress.com/item/x/32272481760.html ?
Feb 05 01:29:42 <karlp> don't believe so, in fact, that's the one I bought, but the page had moved along
Feb 05 01:29:52 <karlp> http://oyewifi.com/ is the producer
Feb 05 01:30:19 <karlp> they have a bunch of packages but I haven't found the source (yet)
Feb 05 01:30:47 <DonkeyHotei> i don't think they posted it
Feb 05 01:30:56 <Zero_Chaos> swalker: hah, I literally just was looking at that
Feb 05 01:31:02 <DonkeyHotei> they have a forum on their site
Feb 05 01:31:30 <karlp> yeah, my chinese isn't so good, but I imagine it won't be terrrribly complicated?
Feb 05 01:32:13 <Zero_Chaos> swalker: I'm thinking += instead of =, no?
Feb 05 01:32:23 <DonkeyHotei> google translate is surprisingly readable
Feb 05 01:32:40 <Zero_Chaos> swalker: otherwise TARGET_*FLAGS won't get in
Feb 05 01:33:06 <karlp> DonkeyHotei: indeed, forums actually seem very empty
Feb 05 01:33:09 <DonkeyHotei> their corporate logo says 哦耶科技
Feb 05 01:33:33 <Zero_Chaos> swalker: I messed up, I messed up bad
Feb 05 01:33:52 <Zero_Chaos> swalker: turns out, "make package/net/aircrack-ng clean" doesn't mean "make -C package/net/aircrack-ng clean"
Feb 05 01:33:58 <Zero_Chaos> swalker: so um, testing may take a while
Feb 05 01:34:03 <DonkeyHotei> i don't know chinese, but google translate has an interesting rendering of that
Feb 05 01:35:15 <karlp> oh yeah technology?
Feb 05 01:35:25 <Zero_Chaos> while I'm rebuilding everything on the planet, where do I add LDFLAGS="--as-needed"?
Feb 05 01:35:27 <karlp> seems to be just  like "oye" to me..
Feb 05 01:35:36 <swalker> Zero_Chaos: .../aircrack-ng/{clean,compile}
Feb 05 01:35:40 <DonkeyHotei> right
Feb 05 01:36:09 <karlp> DonkeyHotei: this guy's router hostname is OYE, looks like it might be the same thing: https://forum.openwrt.org/viewtopic.php?id=52345
Feb 05 01:36:37 <karlp> hope this isn't just late night silly card purchase, I've never used a ramips board before :)
Feb 05 01:36:39 <swalker> Zero_Chaos: my CFLAGS are getting passed already and aircrack looks to only be appending its own CFLAGS
Feb 05 01:38:36 <Zero_Chaos> swalker: any idea how to pass a custom LDFLAG to the whole build system?
Feb 05 01:39:34 <swalker> could throw it in include/package.mk for packages or rules.mk for everything
Feb 05 01:39:57 <DonkeyHotei> karlp: i have a fonera2.0n running, and it's not reliable at all
Feb 05 01:41:05 <DonkeyHotei> the in-tree wifi driver locks up from time to time, and it apparently lacks gigabit eth
Feb 05 01:41:23 <Zero_Chaos> any idea what is failing here? I don't see it http://pastebin.com/9xJryUJt
Feb 05 01:42:32 <swalker> grep -R SSP_SUPPORT package/
Feb 05 01:44:13 <Zero_Chaos> swalker: if that was to me, not really sure what I'm looking for there
Feb 05 01:44:19 * swalker just added it to include/package-defaults.mk's PKG_DEFAULT_DEPENDS instead of chasing down the packages
Feb 05 01:44:20 <karlp> DonkeyHotei: well, will be an adventure for me at least :)
Feb 05 01:45:00 <Zero_Chaos> swalker: oh, you mean it's failing because of the missing dep notice?
Feb 05 01:45:01 <swalker> Zero_Chaos: ethtool is missing a DEPENDS:=+SSP_SUPPORT:libssp
Feb 05 01:45:53 <swalker> (I'm assuming you turned on SSP_SUPPORT)
Feb 05 01:46:19 <Zero_Chaos> swalker: not on purpose, not even sure what that is.
Feb 05 01:47:54 <Zero_Chaos> neoraider: ping
Feb 05 01:47:55 <swalker> Zero_Chaos: grep -i ssp .config
Feb 05 01:48:52 <Zero_Chaos> swalker: ahh, that SSP :-)
Feb 05 01:48:55 <Zero_Chaos> swalker: and oh yeah
Feb 05 01:54:19 <Zero_Chaos> swalker: looks like a few packages need this fix
Feb 05 01:57:25 <swalker> not much build coverage for non-default options
Feb 05 01:58:37 <Zero_Chaos> swalker: good, hardening is sort of a requirement for what I do, so I'll do some good around here with the the right help.  Thanks to you I have opened my first PR on openwrt. thanks!
Feb 05 02:04:40 <Zero_Chaos> swalker: any idea how fast PR's are responded to without poking?
Feb 05 02:04:54 <lst_> dump from main channel...
Feb 05 02:05:10 <lst_> Not sure if anyone has circulated this yet, but the new Eero stuff is going to support OpenWRT out of the box as well. https://www.eero.com/developers
Feb 05 02:05:22 <lst_> If you're looking to pick one up and haven't.. here's my referral link https://www.eero.com?ct-referral-code=yg6lp83s
Feb 05 02:05:26 <lst_> otherwise feel free to do it without the referral link if the product interests you
Feb 05 02:08:16 <lst> sorry, had forgotten to auth
Feb 05 02:14:34 <swalker> Zero_Chaos: where'd you make the PR at?
Feb 05 02:16:30 <Zero_Chaos> swalker: two against openwrt and one against openwrt-packages
Feb 05 02:16:37 <Zero_Chaos> swalker: https://github.com/ZeroChaos-/openwrt/pull/1 https://github.com/ZeroChaos-/openwrt/pull/2
Feb 05 02:19:29 <Zero_Chaos> swalker: so do I just kinda leave those there and the team is pretty good about finding them, or do I poke people, or do I do it some other way?
Feb 05 02:19:36 <swalker> likely a very long time afaik, core issues should be sent as patches to the mailing list, https://dev.openwrt.org/wiki/SubmittingPatches, feeds packages to https://github.com/openwrt/packages
Feb 05 02:20:29 <Zero_Chaos> swalker: I'm not sure patches this simple should go to the ML, but if I get home and no one cares about my PRs still then I'll try that I guess.
Feb 05 02:23:44 <Zero_Chaos> jow_laptop: what say you? should I not be sending pull requests on github like this? https://github.com/ZeroChaos-/openwrt/pull/1
Feb 05 02:38:30 <builder> build #802 of avr32 is complete: Failure [failed compile_5]  Build details are at http://buildbot.openwrt.org:8010/builders/avr32/builds/802
Feb 05 02:46:52 <DonkeyHotei> lst: what's inside?
Feb 05 02:48:11 <lst> https://eero.com/details#tech
Feb 05 02:48:39 <lst> has a USB port as well
Feb 05 02:50:03 <DonkeyHotei> that doesn't say what's inside
Feb 05 02:50:15 <DonkeyHotei> it's just marketing
Feb 05 02:50:18 <lst> as in what processor?
Feb 05 02:50:22 <lst> architecture?
Feb 05 02:50:27 <lst> what info are you looking for?
Feb 05 02:50:28 <lst> :)
Feb 05 02:50:48 <DonkeyHotei> processor, wifi, ram/flash
Feb 05 02:51:00 <lst> ram/flash is on the tech spec page
Feb 05 02:51:23 <lst> dual core 1Ghz, probably Arm I'd guess
Feb 05 02:51:42 <lst> wifi they don't say, but if I hear anything I'll relay
Feb 05 02:51:49 <DonkeyHotei> arm is very diverse
Feb 05 02:52:30 <lst> agreed. I don't work for them... so no idea what they've done yet. I'll find out more
Feb 05 02:52:43 <lst> if they are willing to say anything that is.
Feb 05 02:53:44 <lst> they will likely put up more details soon as well
Feb 05 02:53:51 <lst> they just launched a couple days ago now
**** ENDING LOGGING AT Thu Feb 05 02:59:59 2015