**** BEGIN LOGGING AT Thu Sep 12 02:59:59 2013 Sep 12 10:14:25 qmake2: error while loading shared libraries: __vdso_time: invalid mode for dlopen(): Invalid argument Sep 12 10:15:31 using meta-toolchain-qte Sep 12 10:17:08 any way to fix tis issue ? Sep 12 10:17:37 toolchain built with angstrom-v2013.06-yocto1.4 Sep 12 10:17:59 cd Sep 12 10:18:09 qt-x: which host distro is this on? Sep 12 10:18:21 ubuntu 12.4 lts Sep 12 10:19:27 hmm, we've had a few reports of this Sep 12 10:20:07 I did just test the same thing using poky with 12.04 and I didn't have the issue Sep 12 10:20:28 qt-x: what MACHINE have you set? Sep 12 10:20:36 beaglebone Sep 12 10:21:54 qt-x: I would suggest asking koen on #beagle about this, he should be aware of the problem already, I don't know if he is working on a solution or not Sep 12 10:22:43 should I use oebb.sh to build the toolchain or the sourcing is enough ? Sep 12 10:22:56 using environment-angstrom-v2013.06 Sep 12 10:23:10 I'll be honest and say I'm not too experienced with angstrom's setup scripts Sep 12 10:45:55 bluelightning, really, no issue on oe-core? Sep 12 10:45:59 this is very very weird Sep 12 10:48:19 not in my simple test (build meta-toolchain-qt for qemuarm, and run qmake) Sep 12 11:06:01 qt-x: I'm now again doing some test for the meta-toolchain-qt (not qte) for the raspberry pi Sep 12 11:06:18 qt-x: but I had some troubles using qmake too, it segfaults :/ Sep 12 11:07:00 qt-x: btw when you install the sdk toolchain, you have to source the enviroment from where you installed the sdk ( /usr/local/oecore-i686) Sep 12 11:11:30 fenrig: I did that : Sep 12 11:11:33 which qmake2 Sep 12 11:11:33 /usr/local/oecore-x86_64/sysroots/x86_64-angstromsdk-linux/usr/bin/qmake2 Sep 12 11:12:01 no you have to source the enviroment in /usr/local/oecore-x86_64 Sep 12 11:12:07 but I'm using Qt Sep 12 11:12:11 not Qt embedded Sep 12 11:12:39 qt-x: but I'm now redoing some things :) on another distro Sep 12 11:23:15 bluelightning, does gcc run? Sep 12 11:25:31 there are no meta-toolchain-* in the angstrom layer Sep 12 12:57:54 Crofton|work: Indeed, but the setup scripts fetch oe and yocto too :p Sep 12 12:58:19 I know, I am trying to figure out where the issue could come from Sep 12 13:04:35 hmm, angstrom seems to set gcc to linaro-4.7 for arm Sep 12 21:05:31 Crofton|work, you still around? Sep 12 21:05:42 sort of Sep 12 21:06:44 I'm seriously thinking about moving on to the next bit of hardware... or at least trying a different distro. Nothing should be this hard in 2013. Sep 12 21:07:05 that's what they all say Sep 12 21:07:11 lol Sep 12 21:08:04 hardware is like a woman, it never works just right, take a lot of fiddling and leaves you frustrated in the end. Sep 12 21:08:27 yep Sep 12 21:09:56 I would like to see the logs for the wifi Sep 12 21:10:00 both working and non working Sep 12 21:10:12 they might point us at the problem fairly quickly Sep 12 21:10:17 Crofton|work: get your soft wifi working :-D Sep 12 21:10:28 wifi is not radio! Sep 12 21:10:48 2.4Ghz is well inside radio :-D Sep 12 21:10:58 some judges said otherwise Sep 12 21:11:01 it must be true Sep 12 21:11:02 i'm trying to retrace my steps again... starting with console-image; opkg update, upgrade, then I send logs. that's as far as I got before. Sep 12 21:11:16 Crofton|work: is this the stupid google case again? Sep 12 21:11:20 yep Sep 12 21:11:31 FFS Sep 12 21:11:36 why are they such a range of prices on 2032 batteries on amazon? Sep 12 21:12:41 odd that google complain about NSA and suddenly street view case re-appears Sep 12 21:14:19 maybe I'll try ZigBee/XBee Radios... instead of wifi... Sep 12 21:16:04 rofl Sep 12 21:16:11 get the logs! Sep 12 21:43:09 ok, I have a bine and the screen Sep 12 21:45:59 bone damn it Sep 12 22:25:36 Howdy Sep 12 22:25:49 Does angstrom comes with syslog? Sep 12 22:59:07 it should have something close Sep 12 22:59:10 ls /var/log? **** ENDING LOGGING AT Fri Sep 13 02:59:58 2013