[04:39] <ubuntulov> Hi i would like to install the ubuntu on my android mobile
[04:39] <ubuntulov> my mobile model is micromax QA4501
[04:39] <ubuntulov> is it possible ?
[04:41] <ubuntulov> Can any one able to provide me suggession on this
[06:54] <jalal> Hi there
[06:59] <jalal> help
[11:37] <mardy> zbenjamin, zsombi: hi! Looks like I cannot access the network from inside the LXD container created by the SDK. Any idea how to debug it? There are no tools like ifconfig, route, etc.
[11:59] <zbenjamin> mardy: we will upload new images next week. If you want to fix it:  lxc stop <container> , then use chroot to log into the container, which should give you a working apt
[12:01] <zbenjamin> mardy: probably need to copy /etc/resolv.conf as well from the host
[12:32] <mardy> zbenjamin: thanks!
[12:38] <mardy> zbenjamin: I already created http://askubuntu.com/questions/831915/cannot-access-network-from-lxd-container-created-by-the-ubuntu-sdk a few minutes ago, in case you want to win some easy points :-)
[12:38] <zbenjamin> mardy: did you fix the container already?
[13:03] <mardy> zbenjamin: trying now
[13:06] <mardy> zbenjamin: how do I find the chroot?
[13:06] <zbenjamin> mardy: /var/lib/lxd/containers/<container>/rootfs
[13:09] <mardy> zbenjamin: yes, chroot works, and no need to copy the resolv.conf file
[13:09] <zbenjamin> mardy: nice :)
[13:09] <mardy> zbenjamin: thanks a lot!
[13:10] <zbenjamin> mardy: but that works only for fixing it :). You will not be able to use it like that for compiling
[13:10] <zbenjamin> mardy: sorry for the broken images but our release process is still a bit bumpy
[13:14] <mardy> zbenjamin: a bit unrelated question... the thing I'm building used the xxd command during the build process
[13:14] <mardy> zbenjamin: in the image, do I have to install th armhf version, or the host one?
[13:15] <zbenjamin> mardy: what is it doing?
[13:15] <mardy> zbenjamin: compiling image files into .c files, it's only used during the build process
[13:15] <zbenjamin> mardy: ok so it does not create a binary thats supposed to run on the target device?
[13:16] <mardy> zbenjamin: no
[13:16] <zbenjamin> mardy: in that case its easy and you just install the host one.
[13:16] <mardy> zbenjamin: thought so, but wanted to double-check, thanks!
[13:16] <zbenjamin> mardy: otherwise you'd need a version that runs on x86 but produces armhf binaries
[14:03] <mardy> zbenjamin: did some progress, now I get an error when linking: http://paste.ubuntu.com/23260233/
[14:03] <mardy> zbenjamin: my understanding is that it fails because the chosen linker is gcc and not g++, but I might be wrong
[14:04] <mardy> zbenjamin: the undefined symbol is "new", which is in libstdc++.so
[14:13] <mardy> zbenjamin: got it, the CMAKE_CXX_COMPILER was set to /usr/bin/arm-linux-gnueabihf-gcc; I changed it to s/gcc/g++/, and it worked
[14:14] <mardy> zbenjamin: but I didn't explicitly set it in my project, so I wonder if it's an error in the SDK
[15:20] <mardy> zbenjamin: do you know if we have any click apps using SDL2 in the store?
[15:33] <DanChapman> mardy https://uappexplorer.com/app/balls.briketa uses SDL2
[17:56] <aeoril> I do not see a version port of Ubuntu for the Surface 3.  Is there anyone working on such a thing?
[18:30] <NeKit> aeoril, you should be able to install desktop Ubuntu on it
[18:31] <aeoril> NeKit I tried 16.04 but it would not boot - should I use a later version?
[18:32] <NeKit> well, try searching Linux install instructions for it
[18:32] <NeKit> it should have plenty
[18:32] <aeoril> NeKit: I read something from earlier this month that they were just now going to start putting driver support for the Surface 3 touch screen into the kernel
[18:33] <aeoril> ok
[19:11] <mardy> DanChapman: thanks!
[20:04] <tartare> "sudo mount server:/export /mountpoint" crashes my updated aquaris m10. Is this expexted behaviour?
[20:08] <tartare> What I am actually after is if it is possible to use autofs on the device...