[02:22] <Willdrick> hello o/
[02:23] <Willdrick> I'm trying to flash Ubuntu touch stable to my Nexus 7 2013 but it seems it gets stuck. I've already waited 30 min and nothing happened. Is there something I'm doing wrong?
[02:24] <Willdrick> It's getting stuck at "Flashing version 12 from ubuntu-touch/stable/ubuntu channel and server https://system-image.ubuntu.com to device flo
[02:24] <Willdrick> It's getting stuck at "Flashing version 12 from ubuntu-touch/stable/ubuntu channel and server https://system-image.ubuntu.com to device flo"
[02:25] <Willdrick> I've already retried once and the download is already on cache, so it stuck on there
[05:01] <Kartha> hello
[05:02] <Kartha> is it possible for me to install ubuntu touch on a Samsung Galaxy Grand Neo Plus
[14:11] <Davidrnd> Hello, I've tied to use the click env as cross compiling suite ( https://developer.ubuntu.com/en/blog/2015/04/13/inner-workings-sdk/ ). Under normal curcumstances i had to install my cross compiler and set the LIBRARY_PATH, C_INCLUDE_PATH,CPLUS_INCLUDE_PATH to the specific cross folder ( /usr/include/arm-linux-gnueabihf ). Which path's i have to set for /var/lib/schroot/chroots/click-ubuntu-sdk-15.04-armhf/usr/bin/arm-linux-gnueabihf-
[14:11] <Davidrnd> gcc ?
[14:13] <dobey> Davidrnd: you shouldn't need to manually set any paths really
[14:17] <Davidrnd> dobey: Ok, but if I try to compile it without changing the PATH variables my first error is "/var/lib/schroot/chroots/click-ubuntu-sdk-15.04-armhf/usr/bin/../lib/gcc-cross/arm-linux-gnueabihf/4.9/cc1plus: error while loading shared libraries: libcloog-isl.so.4: cannot open shared " This is because cc1plus need the lib in {click-chroot}/usr/lib/x86_64-linux-gnu/libcloog-isl.so.4
[14:19] <Davidrnd> the paths are relative to the chroot env ( cc1plus ). so it don't work without changing the path var.
[14:19] <Davidrnd> lld cc1plus -> libcloog-isl.so.4 => /usr/lib/x86_64-linux-gnu/libcloog-isl.so.4
[14:19] <dobey> Davidrnd: it's a chroot. you don't build using the things inside the chroot, outside of the chroot.
[14:22] <Davidrnd> dobey: ok, how can I compile outside of the chroot libs/apps with the correct libs regaring ubuntu touch os ?
[14:24] <Davidrnd> dobey: I was able to compile my app by setting up a build env with https://buildroot.org/. But I thought that something similiar is brought by ubuntu itself. So i found click-packages :-) But how QT is able to compile apps with the right dependencies ?
[14:25] <dobey> Davidrnd: the SDK builds the app inside the chroot
[14:28] <mcphail> Davidrnd: you build inside the chroot, installing whatever ARM libs you require therein. You invoke the cross compiler within the chroot (cmake handles this automatically, qmake requires some tweaks, autotools require you to point to the cross-compiler)
[14:29] <Davidrnd> Hmm. so my only chanse is to deploy my cmake project to the chroot and start "click chroot -a armhf -f ubuntu-sdk-15.04 run cmake .." ?
[14:30] <dobey> for varying definitions of "deploy" yes
[14:32] <Davidrnd> dobey: ok. How can I debug such a compiled project ? Script -> gdb-server ?
[14:32] <mcphail> Davidrnd: you can set up your own cross-compiling arrangement if you want, but I don't think anyone else is doing that due to not being masochists
[14:33] <dobey> Davidrnd: you would have to run an ARM binary on an ARM CPU or in an emulator
[14:35] <dobey> Davidrnd: i just use gdb directly on the phone. there are multiple ways to do it. and #ubuntu-app-devel is really the better channel for questions about developing apps and using the SDK and such
[14:37] <Davidrnd> mcphail: I thought, that there's something like a cross-compiling arrangement like for raspberryPi aso. But thanks alot guys.
[14:37] <mcphail> Davidrnd: honestly, learn to love the chroot. It keeps things nicely contained
[14:38] <mcphail> Davidrnd: alternatively - https://adoptingubuntu.wordpress.com/2015/07/10/creating-an-emulated-armhf-chroot-for-development
[14:40] <mcphail> Davidrnd: but that way is _s_l_o_w_
[14:46] <Davidrnd> mcphail: I know. :-) ..
[14:47] <Davidrnd> Thank you guy's have a nice day ;-)
[14:57] <srthhhgfdsha> yyyyyyyyyyyyyyyoooooooooooooooooooooooooooooooooooooooooooooooooooooooooo
[14:57] <srthhhgfdsha> Ubuntu touch for Galaxy S6? someone?
[15:08] <srthhhgfdsha> junkies
[15:11] <dobey> how rude
[15:12] <montvid> oh well
[15:13] <montvid> soo yesterday was a bad day for nexus 7 2013... now im trying to get the ubuntu-kernel guys involved...
[15:15] <montvid> dobey maybe you can change a bugs status from high to critical?
[15:16] <montvid> https://bugs.launchpad.net/canonical-devices-system-image/+bug/1496756
[15:16] <dobey> i cannot
[15:17] <montvid> one cant install and boot the ubuntu touch system. seems critical.
[15:17] <dobey> supporting new devices and what priority that entails, is not a decision that i get to make
[15:17] <montvid> too bad. you seem to be always around
[15:18] <dobey> i am but a lowly developer
[15:18] <montvid> it's not a new device. it works with a patch from github guy :)
[15:19] <dobey> it is a new device. it requires proper testing to support it, and images built with android 5, not just rebuilding a kernel with a random patch from the internet.
[15:20] <montvid> i hope you are not developing for ubuntu touch joke hehe. who knows how many users got neglected by the writing that nexus 7 has official support when it does not.
[15:20] <dobey> and it requires buying a few devices for developers and QA to test it
[15:21] <dobey> no, nexus 7 2013 has support. not 2014 nor 2012 :)
[15:21] <montvid> omg thats a lot
[15:21] <dobey> google screwed up and changed the hardware but not the device codename
[15:22] <montvid> cmon i see guys push just this one little patch and it works
[15:23] <montvid> all the android builds from android 5 work. android 4 works with a patched kernel.
[15:23] <dobey> google doesn't support android 4.4 on it.
[15:24] <montvid> but xda does :D evil
[15:24] <dobey> but arguing about it on irc isn't going to change anything
[15:25] <montvid> guys are booting android 4 with a patched kernel easy.
[15:25] <montvid> google android 4.
[15:27] <montvid> one question. so during ubuntu touch install the kernel is downgraded to android 4? does not matter that the device was running android 6?
[15:28] <dobey> well the aren't companies providing a product and claiming to support it in some official capacity. it's just "here i got this patch to boot a kernel"
[15:28] <montvid> i have to ask that in the kernel channel i guess...
[15:29] <dobey> the "flo" images of ubuntu are based on android 4.4, yes
[15:29] <dobey> and it's not just the kernel
[15:29] <dobey> it's kernel + hal
[15:31] <montvid> i did not have any problems so far running tuoch with the github patch.
[15:31] <montvid> ok ok thank dobey i understand
[15:32] <dobey> sure. and i don't hit many problems that other people have hit, on any of my devices either. it doesn't mean things should be shipped without proper testing. :)
[15:33] <montvid> it just so strange that a github guy fixes that bug in a month and the official devs can't find a better solution in a year.
[15:33] <montvid> i want to be a beta tester!
[15:33] <montvid> hehehe
[15:34] <montvid> now fix my first bug please so i can be one hehe
[15:35] <montvid> well patience is gold
[15:39] <dobey> that's a bit rude
[18:27] <mterry> dobey: I was just testing the u8 snap -- I don't see icons for the snap apps in the click scope.  The fix for that got merged, right?  Is there a known issue or am I seeing something new?
[18:30] <dobey> mterry: when was that snap built? that ual fix only landed last night
[18:31] <mterry> dobey: ah!  I was looking at the date of the package 20170113, not the date of when it migrated from proposed -- that's probably it, will make sure
[18:31] <mterry> yup
[18:31] <mterry> thx
[18:32] <dobey> though, hopefully i can arrange for the click scope to get dropped out of the snap soon now too
[20:16] <TheSpy0> Greetings everyone!