**** BEGIN LOGGING AT Thu Dec 27 02:59:58 2012 Dec 27 04:49:11 hello? Dec 27 04:50:20 hello? Dec 27 16:28:00 is it enough to install "apt-get install build-essential" to have the toolchains to cross-compile C code for beagleboard-Xm? Dec 27 16:28:12 do I need to install apt-get install gcc-4.7-arm-linux-gnueabihf ? Dec 27 16:43:50 I am using gcc-arm-linux-gnueabihf to cross compile, what path do I need to link for libusb-1.0? Dec 27 16:50:55 angs: where every you have the libusb libraries compiled for arm Dec 27 16:51:09 angs: not your local ones that are most likely compiled for x86 Dec 27 16:52:22 I used to link lusb-1.0 on eclipse as /usr/include/libusb-1.0 on "C/c++ general> paths and symbols >library paths" and it was working fine to build the code on my desktop. To cross-compile, I added "/usr/arm-linux-gnueabihf/lib" before "/usr/include/libusb-1.0"", now I get "cannot find -lusb-1.0" error when I build the code. Dec 27 16:52:23 should I copy the libusb-1.0 directory under /usr/arm-linux-gnueabihf/lib Dec 27 16:53:00 or do I suppose to install libusb-1.0 for arm? Dec 27 17:00:47 prpplague: how can I add libusb on arm's gcc ? Dec 27 17:26:04 can anyone tell me how do I suppose to use libusb on ubuntu-arm? Dec 27 17:27:31 angs: did you add libusb files that were complied for arm in the directory - /usr/arm-linux-gnueabihf/lib ? Dec 27 17:34:34 prpplague: I copied libusb* files from /usr/lib to /usr/arm-linux-gnueabihf/lib and libusb-1.0 from /usr/include to /usr/arm-linux-gnueabihf/include however I still have the same problem Dec 27 17:34:45 I get this error when I build the program "skipping incompatible /usr/arm-linux-gnueabihf/lib/libusb-1.0.a when searching for -lusb-1.0" Dec 27 17:35:06 angs: the libusb files in /usr/lib on your host pc are for x86 Dec 27 17:35:12 angs: they are not for arm Dec 27 17:35:23 where can I download libusb files for arm? Dec 27 17:35:53 angs: i would assume there is a ubuntu package you can get, however i alway build them myself Dec 27 17:37:11 prpplague: do you have built libusb files on your machine that you can share? Dec 27 17:37:47 angs: easier for you to do it yourself of find the ubuntu packages Dec 27 17:37:57 angs: what hardware platform are you using? Dec 27 17:38:32 prpplague: I am using beagleboard-Xm. I am a beginner linux user, I do not know how to build package Dec 27 17:39:01 angs: then download the ubuntu pre-built package Dec 27 17:42:22 I already installed libusb-1.0 and libusb-dev, do you know is there any portal to search pre-built package for ubuntu arm? Dec 27 17:43:08 https://launchpad.net/ubuntu/precise/+package/libusb-dev Dec 27 17:43:16 just one example Dec 27 17:43:33 angs: you installed the libusb for you host machine which is x86 Dec 27 17:43:36 not the arm ones Dec 27 17:45:26 prpplague: thank you very much, I am installing the package for beagleboard now Dec 27 17:45:47 angs: google is your friend Dec 27 17:46:50 right, I was using the wrong keyword to search on google. thank you very much for your help Dec 27 17:56:20 prpplague: I have one last question. dpkg -i libusb-dev_0.1.12-20_armhf.deb outputs "package architecture (armhf) does not match system (i386)" error. Do you know if it is possible to install that package under /usr/arm-linux-gnueabihf directory? Dec 27 17:56:58 angs: yea, there should also be a cross compile package somewhere Dec 27 17:59:02 do you know name of the package? Dec 27 18:00:34 angs: no, like i said, i normally build everything from source Dec 27 18:00:48 angs: i am certain there is a howto on the ubuntu wiki pages for what you want to do Dec 27 18:00:53 angs: please check there Dec 27 18:01:09 prpplague: thank you I will check there Dec 28 02:16:26 hello all. im new to this whole irc thing so forgive me if i ask the wrong questions. Has anyone been able to get the sound working in ubuntu installed on galaxy s3 Dec 28 02:17:16 it was able to update itself through update manager but no sound or microphone Dec 28 02:20:17 hey man! Dec 28 02:32:49 anyone direct me to a site that might help with sound issues on a non supported device **** ENDING LOGGING AT Fri Dec 28 02:59:58 2012