**** BEGIN LOGGING AT Wed Apr 06 02:59:58 2016 Apr 06 04:16:14 build #217 of xburst is complete: Failure [failed compile_5] Build details are at http://buildbot.openwrt.org:8010/builders/xburst/builds/217 Apr 06 04:19:39 build #196 of ep93xx is complete: Failure [failed shell_13] Build details are at http://buildbot.openwrt.org:8010/builders/ep93xx/builds/196 Apr 06 04:51:01 build #262 of ramips.rt3883 is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/ramips.rt3883/builds/262 Apr 06 05:07:51 build #253 of x86.64 is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/x86.64/builds/253 Apr 06 07:15:39 build #265 of brcm47xx.legacy is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/brcm47xx.legacy/builds/265 Apr 06 07:19:49 build #242 of rb532 is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/rb532/builds/242 Apr 06 07:35:30 build #267 of ramips.mt7621 is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/ramips.mt7621/builds/267 Apr 06 08:22:21 build #264 of bcm53xx is complete: Failure [failed shell_17] Build details are at http://buildbot.openwrt.org:8010/builders/bcm53xx/builds/264 Apr 06 08:25:10 build #206 of at91 is complete: Failure [failed shell_17] Build details are at http://buildbot.openwrt.org:8010/builders/at91/builds/206 Apr 06 08:30:30 Imre Kaloz 49119 /trunk/package/kernel/mwlwifi/Makefile mwlwifi: upgrade to 10.3.0.17-20160324 Apr 06 12:28:04 anyone else experiencing problems with musl's hostname resolver? Apr 06 12:28:14 ie: root@OpenWrt:~# nslookup google.com Apr 06 12:28:15 nslookup: can't resolve '(null)': Name does not resolve Apr 06 12:28:15 Name: google.com Apr 06 12:28:15 Address 1: 2a00:1450:4001:80e::1000 fra07s63-in-x00.1e100.net Apr 06 12:28:15 ... Apr 06 12:28:31 vs. Apr 06 12:28:38 root@OpenWrt:~# nslookup google.com Apr 06 12:28:38 Server: (null) Apr 06 12:28:38 Address 1: ::1 localhost Apr 06 12:28:38 Address 2: 127.0.0.1 localhost Apr 06 12:28:38 Name: google.com Apr 06 12:30:05 didn't yet notice any particular oddities Apr 06 12:30:12 /etc/hosts is identical, the only (imho significant) difference is that musl is more recent in the top case Apr 06 12:30:35 try nslookup, it shouldn't complain about localhost (or '(null)' for which ever reason) not being resolvable... Apr 06 12:32:10 nope, all fine but I'm not on current trunk Apr 06 12:32:12 ironically, /etc/resolv.conf only contains 'nameserver 127.0.0.1' and doesn't mention any ipv6-specific foo nor hostnames... Apr 06 12:33:31 build #240 of x86.xen_domu is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/x86.xen_domu/builds/240 Apr 06 12:35:59 must have happened somewhen between r47832 and r49096 ... i suspect the musl update(s) which happened during that period... Apr 06 12:36:16 yes the did work on the resolver recently iirc Apr 06 12:39:15 I get that "cant resolve (null) line on my current trunk (yesterday's current at least) Apr 06 12:39:43 it hasn't caused any _problems_ that I've noticed yet though, only see it after trying nslookup as you did. Apr 06 12:40:01 I'm on r48975 fwiw Apr 06 12:40:24 didn't know there'd been that many commits this week! Apr 06 12:42:15 unfortunately it breaks things here: https://gnunet.org/doxygen/d9/d8c/resolver__api_8c.html#a5682f064eb5d3d644c708a3e705b44ba Apr 06 12:43:25 karlp: thanks for confirming! it took quite a while before I noticed that the problem is somewhere in the C-libraries implementation rather than in the code I want to run (and that specific bit wasn't changed in years and thus i was surprised that it suddenly stopped working) Apr 06 13:05:21 in my case it actually _can't_ resolve google.com, it's on a privagte network right now.... Apr 06 13:36:47 karlp: try nslookup localhost, that should always work and not throw any errors... Apr 06 13:51:49 "works" but still prints the line "can't resulve '(null)': Name does not resolve. Still resolves to ::1 and 127.0.0.1 though Apr 06 13:54:00 sure, it works for me to (ie. names are being resolved), but the nameserver itself doesn't, thus the error "can't resolve '(null)': ..." and problems with software relying that resolving localhost and nameserver-info is an indicator for name resolution to be configured correctly Apr 06 13:55:39 I've got in my tree the 15.0.5.1 version changes, but after "make clean; make" I still have build_dir/target-*/root-ar71xx/etc/openwrt_release saying 15.05, and a much older svn revision number? Apr 06 20:19:02 build #261 of lantiq is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/lantiq/builds/261 Apr 06 20:41:28 hmm.... Apr 06 21:58:48 Oh... Apr 06 21:59:24 I guess you shouldn't assume that old packages actually works as intended Apr 06 22:00:40 If you have a list (human readable), what is the prefered format? raw format (as the fs is lzma'd) or gzip? **** ENDING LOGGING AT Thu Apr 07 02:59:58 2016