=== RAFA is now known as Guest33816 === nemo_ is now known as nemo === chihchun_afk is now known as chihchun [10:07] Hi to all ! Can some body help me, in what paths my app can write data ? [10:08] Because i am trying right now to write some cache inside my app folder, but app armor denied [18:12] OK, now confused. I'm on 14.04, attempting to build a C++ app in Qt Creator using my 14.10 arm chroot. If I re-run cmake in Qt Creator (right-click project name in left sidebar, say "Run CMake"), it throws the error "g++ version must be at least 4.9!". Now, the gcc in my 14.04 machine is indeed 4.8.4, but in the chroot it is not; it is 4.9.1. [18:13] so this should work, right? But... no. So... help? [18:14] also, appdevs ^ :) [18:28] and it's definitely using the kit and not building on your desktop? [18:28] I don't know how to know that :( [18:29] certainly I haven't changed anything about the build code, and it has built in the past -- it's an armhf chroot which builds for the phone, so if it were entirely using my desktop's stuff, it'd fail when installed tothe phone 'cos the desktop is amd64 [18:29] and the build output says: [18:29] Command returned 1: schroot -c 'click-ubuntu-sdk-14.10-armhf-ucca-1000-{807325e9-3c48-498f-825b-80767f03ac79}' --run-session -- env DEB_BUILD_ARCH=amd64 DEB_BUILD_ARCH_BITS=64 DEB_BUILD_GNU_CPU=x86_64 DEB_BUILD_MULTIARCH=x86_64-linux-gnu DEB_BUILD_ARCH_CPU=amd64 DEB_HOST_GNU_TYPE=arm-linux-gnueabihf DEB_HOST_GNU_SYSTEM=linux-gnueabihf DEB_BUILD_GNU_SYSTEM=linux-gnu DEB_BUILD_ARCH_ENDIAN=little DEB_HOST_GNU_CPU [18:29] =arm DEB_HOST_ARCH_OS=linux DEB_HOST_ARCH=armhf DEB_HOST_MULTIARCH=arm-linux-gnueabihf DEB_HOST_ARCH_CPU=arm DEB_HOST_ARCH_ENDIAN=little DEB_HOST_ARCH_BITS=32 DEB_BUILD_GNU_TYPE=x86_64-linux-gnu DEB_BUILD_ARCH_OS=linux cmake /home/aquarius/Programs/Others/addtodash '-GCodeBlocks - Unix Makefiles' [18:29] click projects on the left [18:30] why are you building in a 14.10 chroot? [18:30] which certainly looks like it's building on the phone. [18:30] you should be on a 15.04 chroot [18:30] IMO [18:30] (and only the "Bq E4.5 Ubuntu (GCC armhf)" kit is being used. [18:31] Mainly because I haven't set up a 15.04 chroot yet, because the 14.10 one works fine. [18:31] i would [18:31] i recently updated my 15.04 because it build broken binaries [18:31] I even added the stable ppa to my chroot [18:31] and now it builds things that work :S [18:31] mine builds things that work -- it did a week ago, anyway :) [18:31] agreed that I should at some point set up a new one [18:32] but the whole area of kits and chroots is terribly confusing and I am loath to abandon a working thing :) [18:33] pfff [18:33] just do this:- [18:33] click chroot -a armhf -f ubuntu-sdk-15.04 create [18:33] with sudo [18:33] and leave it running [18:34] currently reading up on how to create a new kit. [18:34] (I know the command line works, but I don't wanna do it that way.) [18:34] i only interact with the sdk via the command line [18:35] I don't use qtc at all anymore [18:35] i am the exact opposite :) [18:35] :) [18:35] all bases covered [18:36] "Managing targets and kits" under https://developer.ubuntu.com/en/apps/sdk/tutorials/click-targets-and-device-kits/ seems to be the way [18:36] now to wait a hundred years while I download a whole debian archive again ;) [18:39] let's see if this fixes things, at least. [19:24] popey, that does seem to have fixed the previous issue, indeed, now that I'm building in a 15.04 chroot. So, I get dragged kicking and screaming into the modern day, again :) [19:34] :) [19:34] well, also, 14.10 isn't even supported anymore [19:37] apps built with it should still work, though [19:38] that's what version numbering of the components is for. :)