**** BEGIN LOGGING AT Tue Aug 27 02:59:58 2013
Aug 27 13:18:27 <cfo215_> getting AttributeError: 'module' object has no attribute 'lib' trying to run opkg-target update after sourcing /usr/local/angstrom/environment-setup...  see http://pastebin.com/pAgsW8uF for details
Aug 27 14:15:15 <cfo215_> is there an IRC for angstrom/yocto bitbaking support?  Cause I don't think this is it.
Aug 27 14:51:05 <cverster> Hello! When I install mysql5 on angstrom, it say it cannot connect to the server through socket "/tmp/mysql.sock", but if I look in tmp, there is not even a mysql.sock file. How should that file look?
Aug 27 14:54:07 <bluelightning> cverster: is mysqld running?
Aug 27 14:56:04 <cverster> bluelightning: it says "./mysqld: line 3: /etc/default/rcS: No such file or directory" when I try to run it
Aug 27 14:56:33 <bluelightning> hmm...
Aug 27 15:00:45 <bluelightning_> cverster: hmm, that's only installed with sysvinit, which angstrom doesn't use
Aug 27 15:00:56 <bluelightning_> cverster: I suspect this hasn't been tested in a systemd-only environment
Aug 27 15:01:11 <cverster> so no sql for me?
Aug 27 15:01:40 <bluelightning_> cverster: well, you may just be able to comment out that line
Aug 27 15:04:47 <cverster> bluelightning: thanks, attempting that now
Aug 27 15:13:20 <cfo215_> Can anyone help with this? $ arm-angstrom-linux-gnueabi-gcc --version
Aug 27 15:13:20 <cfo215_> arm-angstrom-linux-gnueabi-gcc: error while loading shared libraries: __vdso_time: invalid mode for dlopen(): Invalid argument
Aug 27 15:14:48 <cfo215_> I used MACHINE=beaglebone ./oebb.sh bitbake meta-toolchain to build the tool chain and use the generated sh script from the SDK to install it.
Aug 27 15:16:41 <cfo215_> The generated shell script was named "angstrom-eglibc-x86_64-cortexa8hf-vfp-neon-v2013.06-toolchain.sh"
Aug 27 15:17:59 <cfo215_> My development machine is x86_64 Ubuntu 12.04.2
Aug 27 15:19:33 <cfo215_> and I did "$ source /usr/local/oecore-x86_64/environment-setup-cortexa8hf-vfp-neon-angstrom-linux-gnueabi" prior to trying the arm-angstrom-linux-gnueabi-gcc --version
Aug 27 15:20:12 <cfo215_> Any insights to what I'm doing wrong would be greatly appreciated.  Thanks
Aug 27 17:08:30 <cfo215> Does anyone here actually develop anything using the Angstrom tool chains generated by OE/Yocto?
Aug 27 17:09:37 <cfo215> from the angstrom-v2013.06-yocto1.4 git branch that is?
Aug 27 17:11:39 <Crofton|work> I ahve done cross compiles from sdk's extracted from images
Aug 27 17:12:27 <cfo215> Crofton, from that specific branch?
Aug 27 17:13:32 <cfo215> are you referring to the images from http://www.angstrom-distribution.org/toolchains/ or ones you've created using OE/Yocto bitbake?
Aug 27 17:14:24 <Crofton|work> I jsut work off master
Aug 27 17:14:34 <Crofton|work> I ahven't tried the ones rom tehre
Aug 27 17:14:40 <Crofton|work> what is your probelm?
Aug 27 17:15:40 <cfo215> Crofton, most recently:  "qmake2: error while loading shared libraries: __vdso_time: invalid mode for dlopen(): Invalid argument" using the toolchain created from the above mentioned branch.
Aug 27 17:16:21 <cfo215> Crofton|work, I can't use the Master because it doesn't support the Beaglebone Black.
Aug 27 17:16:36 <Crofton|work> so you run qmake2 from the toolcahin binary dir
Aug 27 17:17:52 <cfo215> Crofton|work, no, I source the environment as described at  http://www.angstrom-distribution.org/toolchains/ and then run qmake.  I'll try the fqn to the bin.
Aug 27 17:18:22 <Crofton|work> which qmake2
Aug 27 17:18:37 <Crofton|work> then try ldd on the qmake binary to see what it is linking against
Aug 27 17:18:50 <cfo215> /usr/local/oecore-x86_64/sysroots/x86_64-angstromsdk-linux/usr/bin/qmake2
Aug 27 17:19:31 <cfo215> $ ldd /usr/local/oecore-x86_64/sysroots/x86_64-angstromsdk-linux/usr/bin/qmake2
Aug 27 17:19:31 <cfo215> 	linux-vdso.so.1 =>  (0x00007fff8c7a8000)
Aug 27 17:19:31 <cfo215> 	libstdc++.so.6 => /usr/local/oecore-x86_64/sysroots/x86_64-angstromsdk-linux/usr/bin/../../usr/lib/libstdc++.so.6 (0x00007f3e84880000)
Aug 27 17:19:31 <cfo215> 	libm.so.6 => /usr/local/oecore-x86_64/sysroots/x86_64-angstromsdk-linux/usr/bin/../../lib/libm.so.6 (0x00007f3e84580000)
Aug 27 17:19:34 <cfo215> 	libgcc_s.so.1 => /usr/local/oecore-x86_64/sysroots/x86_64-angstromsdk-linux/usr/bin/../../lib/libgcc_s.so.1 (0x00007f3e84368000)
Aug 27 17:19:37 <cfo215> 	libc.so.6 => /usr/local/oecore-x86_64/sysroots/x86_64-angstromsdk-linux/usr/bin/../../lib/libc.so.6 (0x00007f3e83fb8000)
Aug 27 17:19:40 <cfo215> 	/lib64/ld-linux-x86-64.so.2 (0x00007f3e84b88000)
Aug 27 17:19:42 <cfo215> christos@christos-500-054:~/qte-example$ ldd /usr/local/oecore-x86_64/sysroots/x86_64-angstromsdk-linux/usr/bin/qmake2
Aug 27 17:20:22 <cfo215> Crofton|work, looks correct from my newb perspective
Aug 27 17:21:26 <Crofton|work> you are running on a 64 bit distro?
Aug 27 17:21:28 <cfo215> Crofton|work,  except for the "/lib64/ld-linux-x86-64.so.2" that is.
Aug 27 17:21:59 <cfo215> Crofton|work,  Trying to cross-compile on 64 bit Ubuntu 12.04.2
Aug 27 17:22:22 <cfo215> Crofton|work, target is ARM/Beaglebone Black
Aug 27 17:22:25 <Crofton|work> you might try asking in #yocto
Aug 27 17:23:04 <cfo215> funny... they always tell me I should ask in #angstrom...
Aug 27 17:24:09 <Crofton|work> well, we've triaged the issue some
Aug 27 17:24:23 <Crofton|work> I've never run qmake
Aug 27 17:24:34 <Crofton|work> and am not sure abot the dlopen stuff
Aug 27 17:24:47 <Crofton|work> go ahead and put the output of ldd in pastebin
Aug 27 17:27:21 <cfo215> Crofton|work, http://pastebin.com/n057BH88
Aug 27 17:27:56 <Crofton|work> now paste that and the erro in #yocto
**** ENDING LOGGING AT Wed Aug 28 02:59:58 2013