**** BEGIN LOGGING AT Sun Nov 15 02:59:58 2015 Nov 15 20:12:47 /home/fmee/projects/yocto/rpi-build/tmp/work/arm1176jzfshf-vfp-poky-linux-gnueabi/ntopng/1.0-r0/git/configure: line 3304: syntax error near unexpected token `(' Nov 15 20:13:03 /home/fmee/projects/yocto/rpi-build/tmp/work/arm1176jzfshf-vfp-poky-linux-gnueabi/ntopng/1.0-r0/git/configure: line 3304: ` $as_echo_n "(cached) " >&6' Nov 15 20:13:07 configure failed Nov 15 20:13:24 only happens when i run this configure within the context of yocto Nov 15 20:13:32 any ideas? Nov 15 20:16:26 normally i would expect a problem with process substitution Nov 15 20:16:45 aka. /bin/sh not being bash Nov 15 20:20:20 without enough info, my only guess is that you have a bad m4 rule.. or someone hand patched configure -- and running autoconf has removed the hand patching Nov 15 20:23:06 fray: https://paste.kde.org/paccnva9j Nov 15 20:24:46 bitbake -c devshell Nov 15 20:24:54 try runnign configure manually same error? Nov 15 20:25:01 fray: yes Nov 15 20:25:04 (I suspect it's the trailing ':' Nov 15 20:25:20 likely a bad m4 rule that defiles ac_cv_lib_pcap_pcap_open_live Nov 15 20:25:27 -defines- Nov 15 20:26:35 this works in the devshell: if ${ac_cv_lib_pcap_pcap_open_live+:} false; then :; echo "(cached)"; else echo "bla"; fi Nov 15 20:26:50 i was wondering if the trailing : has a purpose Nov 15 20:27:10 : is supposed to be a no-op in shell.. but being at the end of the line like that, I don't know what it's actually going to do Nov 15 20:27:15 https://stackoverflow.com/questions/3224878/what-is-the-purpose-of-the-colon-gnu-bash-builtin Nov 15 20:27:55 remember it's also running under whatever configure's defined shell is.. likely /bin/sh which may be dash Nov 15 20:28:29 fray: right. this was my initial thinking Nov 15 20:28:40 and i wondered what this means for yocto Nov 15 20:29:08 the rror though you reported (about having problems '( or )') indicates though it's likely earlier and an errant " or ' Nov 15 20:29:23 this is a package problem or a host (shell) problem.. not sure which.. Nov 15 20:29:50 you can always load the configure in vim, search to that line and see if the color coding indicates any problems (not fool proof, but often helps) Nov 15 20:32:12 changed /bin/sh from dash to bash. same problem Nov 15 20:32:37 ya, then it's likely m4.. you need to try to figure out where in the generated shell script it's failing.. Nov 15 20:32:45 it'll be somewhere at or before the error point.. Nov 15 20:32:50 ok, thanks Nov 15 20:32:55 sorry couldn't be more helpful Nov 15 20:37:14 fray: no worries. Nov 15 21:02:47 changing $as_echo_n "(cached) " >&6 to $as_echo_n "cached " >&6 makes the script work Nov 15 21:03:22 aka. removing the parens Nov 15 21:03:38 this is strangely enough also true if the line is commented out?! Nov 15 21:07:06 before this like there is a " missing somewhere Nov 15 21:13:26 fray: i tried to use "set -x" to debug it. from what i am seeing there i am not missing a " Nov 15 21:14:46 on the other hand the shell fragment work fin in isolation Nov 15 21:14:48 ... Nov 15 21:14:57 so i am not ruling it out :-) Nov 15 21:16:24 looks like a missing quote to me. would explain why it has an effect commented, if the comment char is part of the encompassing string, and the first of the two quotes on that line ends that string, while the second starts another.. Nov 15 21:19:26 kergoth, fray: found it. missing end quote. Nov 15 21:19:29 thanks1 Nov 15 21:19:30 ! Nov 15 21:19:41 *pfff* that caused me a lot of grief Nov 15 23:57:05 Using fido I've built core-imagine-minimal with some additional packages under the qemuarm machine type however the tmp/deploy/images/qemuarm folder only has rootfs files and no kernel. The only indication of an issue I see relating to this is a warning on multiple providers of virtual kernel but even when I specify one it doesn't build me a kernel bin file. Nov 15 23:57:40 (I'm just trying to run using runqemu to test out my image) Nov 16 00:18:56 I'm going to be afk, I'll check back in a while if there are any suggestions, thanks for any support :-) **** ENDING LOGGING AT Mon Nov 16 02:59:58 2015