**** BEGIN LOGGING AT Sun Jul 29 03:00:00 2018
Jul 29 07:10:41 <elvispre> Morning!
Jul 29 07:13:58 <Herrie> Morning!
Jul 29 08:47:47 <saidinesh5> Bahhh crappy webkit!
Jul 29 08:47:48 <saidinesh5> g++: error: unrecognized command line option ‘-std=c++14’
Jul 29 08:57:18 <saidinesh5> do i have to do anything to trigger a rebuild of the packages?
Jul 29 08:57:26 <saidinesh5> i previously built everything with gcc 4.x
Jul 29 08:57:31 <saidinesh5> and now just installing gcc7
Jul 29 08:57:41 <saidinesh5> iirc there was an abi breakage at gcc5
Jul 29 09:00:31 <elvispre> I was going to check online, but webos-ports.org is down right now.
Jul 29 09:01:11 <elvispre> gcc --version is 5.4 on my build VM.
Jul 29 09:01:40 <saidinesh5> Ahh
Jul 29 09:01:59 <saidinesh5> i think there is no abi breakage between 5 and 7
Jul 29 09:02:03 <saidinesh5> so i don't think that should be an issue
Jul 29 09:02:10 <saidinesh5> elvispre: how do i trigger a whole rebuild?
Jul 29 09:02:25 <saidinesh5> MACHINE=qemux86 bitbake -k luneos-dev-emulator-appliance
Jul 29 09:02:27 <saidinesh5> this is what i was using
Jul 29 09:02:51 <elvispre> I don't use -k usually. Is that "keep going even if there is an error"?
Jul 29 09:02:54 <saidinesh5> i think triggering a full rebuild would be a good idea because otherwise i don't think the libraries created by one would link well with the other
Jul 29 09:02:55 <saidinesh5> Ahh
Jul 29 09:03:29 <elvispre> "rm -rf tmp-glibc" is one way. It is the most drastic way though.
Jul 29 09:03:44 <saidinesh5> yeah that will cause even redownload right?
Jul 29 09:03:49 <elvispre> "bitbake -f" forces a package rebuild.
Jul 29 09:04:07 <elvispre> There may be a "bitbake rebuild" command.
Jul 29 09:04:34 <saidinesh5> Aye . replaced -k with -f
Jul 29 09:04:54 <elvispre> Yes, removing tmp-glibc, cache, sstate and download folders is "scorched earth".
Jul 29 09:05:12 <saidinesh5> cache holds the downloaded items?
Jul 29 09:05:15 <elvispre> I have been known to delete my build VM and just create a new one :-)
Jul 29 09:05:22 <saidinesh5> hahha
Jul 29 09:05:24 <nizovn> i think needed gcc version is being built by bitbake itself
Jul 29 09:05:47 <elvispre> Not sure what cache stores.
Jul 29 09:05:48 <saidinesh5> nizovn: so why would it whine about missing c++14 when building webengine
Jul 29 09:05:51 <nizovn> not sure your host compiler matters
Jul 29 09:06:12 <nizovn> i would like to see logs..
Jul 29 09:06:51 <elvispre> nizovn: Good point!
Jul 29 09:08:34 <saidinesh5> https://bpaste.net/show/d8dbc50c4049
Jul 29 09:10:37 <saidinesh5> and the current error: https://bpaste.net/show/01cb43271c9c
Jul 29 09:10:51 <saidinesh5> this time while building some buildsystem for webengine
Jul 29 09:12:12 <saidinesh5> crazy C++ buildsystems.. you'd think after 30 years, they would standardize one and get it done with. now to build a project you build it's build system first..
Jul 29 09:14:37 <nizovn> it makes sense to build gcc for embedded systems as we are doing cross-compilation
Jul 29 09:14:50 <elvispre> OK, inspecting my tmp-glibc content I see that we build (and then use) gcc-6.4. (Couldn't remember off hand.)
Jul 29 09:17:53 <saidinesh5> nizovn: oh sure.. even for cross compiling to windows/openwrt it is usually a good idea to build the toolchain first
Jul 29 09:18:12 <saidinesh5> btw. did you see any issues in the logs i posted?
Jul 29 09:18:23 <elvispre> And, incidentally, with a mako and an onyx build currently built, that is using almost 100 GB of my drive.
Jul 29 09:19:15 <saidinesh5> Ahh
Jul 29 09:19:28 <saidinesh5> doing this on my HDD right now. so space isn't a constraint B)
Jul 29 09:20:41 <nizovn> saidinesh5: not yet, but in your second log OE_QMAKE_COMPILER is being passed correctly
Jul 29 09:22:37 <elvispre> "Empty sources for copy" says to me "I ran out of memory last time and left some empty files lying around."
Jul 29 09:22:55 <elvispre> Did you have a failed build before?
Jul 29 09:23:25 <saidinesh5> yes
Jul 29 09:23:35 <saidinesh5> but before it failed because of the c++14 thing
Jul 29 09:25:31 <elvispre> Yes, that is a bit odd, isn't it?
Jul 29 09:25:36 <saidinesh5> yup
Jul 29 09:26:06 <saidinesh5> I think it was trying to use host compiler to build it's build system
Jul 29 09:26:26 <saidinesh5> and the toolchain built by it to compile it's targets
Jul 29 09:29:08 <saidinesh5> so how do i make it restart compilation for this qtwebengine?
Jul 29 09:29:57 <elvispre> In meta-smartphone: "git stash". Then up the top, "make update" and return to meta-smartphone. "git stash pop": No stash found. Grrr!
Jul 29 09:30:22 <saidinesh5> ls
Jul 29 09:30:37 <elvispre> saidinesh5: Just try bitbake qtwebengine
Jul 29 09:30:47 <elvispre> If that doesn't work add "-f"
Jul 29 09:31:46 <saidinesh5> -f isn't working either
Jul 29 09:31:48 <nizovn> MACHINE=qemux86 bb qtwebengine -f -c compile
Jul 29 09:32:53 <saidinesh5> same error
Jul 29 09:33:03 <saidinesh5> i think it was trying to use the cache
Jul 29 09:34:24 <Herrie> You can also try MACHINE=qemux86 bb -f qtwebengine -c clean
Jul 29 09:34:33 <Herrie> Then MACHINE=qemux86 bb -f qtwebengine
Jul 29 09:35:21 <saidinesh5> wow ... just do_clean is taking like so long
Jul 29 09:36:02 <Tofe> Morning!
Jul 29 09:36:09 <saidinesh5> Afternoon!
Jul 29 09:36:11 <saidinesh5> lol
Jul 29 09:36:29 <saidinesh5> okay thankfully it doesn't have to reclone/download it
Jul 29 09:36:34 <saidinesh5> just unpacking it now
Jul 29 09:37:57 <saidinesh5> out of curiosity, are there any i586 devices that you are actually targetting?
Jul 29 09:38:00 <elvispre> Just for fun, I have set off a luneos-dev-emulator-appliance myself. I'll let you know how I get on.
Jul 29 09:38:06 <saidinesh5> (why not just use i686 that is..)
Jul 29 09:38:34 <Tofe> saidinesh5: just qemu-x86
Jul 29 09:38:39 <saidinesh5> Ahh
Jul 29 09:39:02 <saidinesh5> So after this build, I would probably have to search for and add support for an intel cherrytrail layer
Jul 29 09:39:28 <Tofe> interesting
Jul 29 09:39:34 <saidinesh5> they even have some good chromium patches too to drastically reduce ram consumption and speed up performance
Jul 29 09:39:37 <Tofe> but unknown territory yet :p
Jul 29 09:39:43 <saidinesh5> yup. for me too
Jul 29 09:40:08 <saidinesh5> this is my first yocto build...
Jul 29 09:40:09 <saidinesh5> bah
Jul 29 09:40:11 <saidinesh5> same error
Jul 29 09:41:28 <saidinesh5> https://bpaste.net/show/c40e9809e03a
Jul 29 09:46:32 <saidinesh5> did it fail to compile something ? or build some dependency for this ?
Jul 29 09:51:41 <Tofe> try "bb -f cleansstate qtwebengine && bb qtwebengine"
Jul 29 09:51:46 <Tofe> oops
Jul 29 09:51:52 <Tofe> "bb -f -c cleansstate qtwebengine && bb qtwebengine"
Jul 29 09:52:12 <Tofe> that's clean up the current qtwebengine build, and its build cache, and restart it
Jul 29 10:01:03 <saidinesh5> same error
Jul 29 10:01:19 <saidinesh5> copy("layout_test_data_mojo_bindings")
Jul 29 10:01:35 <saidinesh5> that sounds like a webos thing
Jul 29 10:01:54 <nizovn> it's coincidence :P
Jul 29 10:02:26 <saidinesh5> Ah
Jul 29 10:19:15 <saidinesh5> elvispre: how did your build come along?
Jul 29 10:19:48 <elvispre> Just installing mesa. 5330 out of 5685...
Jul 29 10:20:03 <saidinesh5> that was fast...
Jul 29 10:20:07 <saidinesh5> probably the webengine is done
Jul 29 10:20:21 <elvispre> Didn't spot it yet.
Jul 29 10:20:26 <saidinesh5> oh
Jul 29 10:20:53 <elvispre> Building qtbase now, so qtwebengine to follow shortly, I expect.
Jul 29 10:21:34 <saidinesh5> yup
Jul 29 10:45:02 <saidinesh5> let me know if your build fails too
Jul 29 10:47:26 <elvispre> Sure will. qtbase and then qtdeclarative held things up as everything else depends on them. I have seen memory usage peak around 33 GB with 16 builds, several of which being qt* compile steps.
Jul 29 10:49:46 <saidinesh5> you're tempting me to build a machine like that myself
Jul 29 10:50:13 <saidinesh5> started the build yesterday night and was done - well errored this morning
Jul 29 10:51:20 <elvispre> Well, building this stuff is a pretty special case. You don't need these kind of resources just to do a bit of web surfing or even regular code development.
Jul 29 10:52:03 <elvispre> Finally compiling qtwebengine...
Jul 29 10:52:29 * saidinesh5 holds his breath
Jul 29 10:52:41 <elvispre> Step 5626 of 5685.
Jul 29 10:53:15 <elvispre> I wouldn't hold your breath. If it doesn't error it may well take ~50 minutes on its own.
Jul 29 10:58:37 <saidinesh5> oh
Jul 29 11:27:58 <elvispre> saidinesh5: qtwebengine built no problem here.
Jul 29 11:28:06 <saidinesh5> O_o
Jul 29 11:28:37 <saidinesh5> so what do i redo?
Jul 29 11:31:49 <elvispre> Difficult to say. I guess you had a build error before the qtwebengine one.
Jul 29 11:32:47 <Tofe> saidinesh5: what is your build environment ? ubuntu chroot ? archlinux ?
Jul 29 11:32:51 <elvispre> Just a thought. If you are using ubuntu 16.04 (or similar) did you spot the need to do apt-get install gcc-multilib g++-multilib
Jul 29 11:32:59 <saidinesh5> ubuntu trusty chroot Tofe
Jul 29 11:33:34 <saidinesh5> used to build and gcc-multilib is already installed
Jul 29 11:33:39 <elvispre> I am using ubuntu 16.04. It's a VM so I can just follow the instructions on webos-ports.org exactly.
Jul 29 11:33:55 <saidinesh5> VM as in virtualbox?
Jul 29 11:34:37 <elvispre> VM as in Windows' Hyper-V but I used to use VMware with equal success.
Jul 29 11:34:42 <Tofe> saidinesh5: I'm on 16.04 (xenial)
Jul 29 11:34:46 <saidinesh5> Ahh
Jul 29 11:34:58 <saidinesh5> I can set up a chroot of that..
Jul 29 11:35:13 <Tofe> trusty is a bit old, maybe noone ever tried it recently and something broke.
Jul 29 11:35:44 <Tofe> Of course that would mean the qtwebengine is still dependent on something in the host OS, which is bad, but that can happen
Jul 29 11:35:53 <Tofe> +build
Jul 29 11:36:28 <saidinesh5> yup
Jul 29 11:36:33 <saidinesh5> give me 10 minutes
Jul 29 11:36:38 <saidinesh5> will setup a 16.04 chroot
Jul 29 11:36:48 <Tofe> ok :)
Jul 29 11:37:09 <Tofe> in that case you'll have quite the same thing as me: a 16.04 chroot inside an x64 archlinux
Jul 29 11:37:10 <saidinesh5> amd64?
Jul 29 11:37:19 <Tofe> yup
Jul 29 11:39:28 <elvispre> Tofe: Are you trying Nougat or Oreo as the base for the A1 currently?
Jul 29 11:40:02 <elvispre> I am having no luck installing an old "experimental" lineageOS-14.1 on mine.
Jul 29 11:40:48 <elvispre> 15.1 probably wants "the Oreo scheme" by the look of it, if that makes any sense.
Jul 29 11:41:08 <saidinesh5> https://github.com/CM-CHT
Jul 29 11:41:20 <saidinesh5> seems useful
Jul 29 11:41:36 <saidinesh5> but i think it would be nicer to go via. direct yocto right?
Jul 29 11:41:47 <saidinesh5> instead of this + hybris
Jul 29 11:41:56 <Tofe> elvispre: I'm on Nougat
Jul 29 11:42:42 <Tofe> elvispre: I didn't install lineageOS, I install stock ROM 7.1, which is AndroidOne, i.e. nearly AOSP
Jul 29 11:43:08 <elvispre> Tofe: Right.
Jul 29 11:43:32 <Tofe> saidinesh5: direct Mesa stack would make more sense, if that's possible
Jul 29 11:44:11 <Tofe> currently we're using an old Mesa version, because later they removed eglfs support
Jul 29 11:44:17 <saidinesh5> Yeah.. i think it should be available.. there was an intel-aero
Jul 29 11:44:17 <elvispre> Tofe: If I could succeed in installing LineageOS, I would feel more in control of the device.
Jul 29 11:44:20 <saidinesh5> oh
Jul 29 11:44:36 <saidinesh5> without eglfs would we have a GUI at all?
Jul 29 11:45:02 <Tofe> saidinesh5: well we need an EGL driver, whatever it is
Jul 29 11:45:22 <saidinesh5> mesa should work well enough right with intel gpu?
Jul 29 11:45:28 <saidinesh5> and upstream kernel
Jul 29 11:45:41 <Tofe> I guess so; as said before, it has never been tried
Jul 29 11:45:50 <saidinesh5> yup
Jul 29 11:46:26 <Tofe> elvispre: where did you fetch it?
Jul 29 11:47:25 <elvispre> Tofe: 14.1 from some XDA forum post. (Looked pretty legit.) 15.1 from LineageOS downloads.
Jul 29 11:54:45 <Tofe> elvispre: "If coming from Oreo, then flash Nougat stock firmware & wipe Internal Storage"
Jul 29 11:56:10 <elvispre> Tofe: I was running Nougat though. I tried following their instructions on what to wipe and that is why I am now running flash_all.bat!
Jul 29 11:56:28 <Tofe> :) ok
Jul 29 11:57:03 <elvispre> Instructions, I can follow. Unwritten rules, that's a bit harder :-)
Jul 29 11:57:27 <elvispre> Evidently, I must be doing something wrong, but what?
Jul 29 11:58:22 <Tofe> I don't know :/
Jul 29 11:59:16 <Tofe> elvispre: https://forum.xda-developers.com/mi-a1/development/rom-lineage-os-14-1-t3750652 this one ?
Jul 29 12:00:25 <elvispre> Looks familiar.
Jul 29 12:00:49 <elvispre> "Magisk(mandatory)". Hmmm.
Jul 29 12:03:58 <elvispre> I guess that is what I was missing.
Jul 29 12:06:26 <Tofe> why would that be mandatory ? It's only to be able to be root, afaik
Jul 29 12:08:34 <elvispre> I agree but the red words do say "If you face boot splash, then that means you haven't flashed Magisk!"
Jul 29 12:09:48 <elvispre> Perhaps I will try Oreo and LineageOS-15.1 which states that rooting is optional.
Jul 29 12:15:29 <Tofe> ok
Jul 29 12:59:43 <saidinesh5> bah what is this day
Jul 29 12:59:49 <saidinesh5> even my debootstrap is consistently failing
Jul 29 13:00:32 <Tofe> :)
Jul 29 13:03:49 <saidinesh5> aand my mouse batteries died
Jul 29 13:13:02 <elvispre> I find this so weird. These LineageOS zip files are advertised as specifically for this device (Tissot) but the installation instructions simply do not work.
Jul 29 13:13:49 <elvispre> When I come to install any of them, they just turn out to refer to partitions / devices that do not exist and they fail almost immediately.
Jul 29 13:14:48 <saidinesh5> elvispre: maybe your device's partition layout changed/is different?
Jul 29 13:14:56 <saidinesh5> xiaomi does that with a lot of devices
Jul 29 13:15:13 <saidinesh5> on my cancro initially it had 2 partitions for everything except data
Jul 29 13:15:30 <saidinesh5> then for android6 update, it issued a firmware update which merged all those partitions
Jul 29 13:15:33 <elvispre> But surely LineageOS would know about that and write the zip content accordingly.
Jul 29 13:15:57 <saidinesh5> nope. even if they did,they probably expect you to install that firmware first, so it has the correct partitions
Jul 29 13:16:18 <saidinesh5> that's what i did anyway. for sailfish, i based my port on the newer partition layout and asked people to first install that xiaomi update
Jul 29 13:16:40 <saidinesh5> i wouldn't be surprised if the same is the case with your device, given how this device didn't come out with treble but now probably supports treble
Jul 29 13:20:08 <elvispre> If they expect me "to install that firmware first", they should say so.
Jul 29 13:21:25 <saidinesh5> yeah.. plus the device is probably released in so many places that each come with their own firmware version.. i have had so many people telling me they couldn't install my ROM on their chinese firmware
Jul 29 13:23:51 <elvispre> Interesting (and I am accumulating plenty of evidence to back that up).
Jul 29 13:24:31 <saidinesh5> yeah.. since your device is very new.. i am assuming you guys got the treble layout
Jul 29 13:25:04 <elvispre> No idea.
Jul 29 13:25:51 <saidinesh5> my memory is a little fuzzy on this...
Jul 29 13:25:59 <saidinesh5> but see if you have a /vendor partition?
Jul 29 13:26:11 <saidinesh5> previously the vendor used to be just a /system/vendor directory iirc
Jul 29 13:26:16 <saidinesh5> and they changed this too with treble
Jul 29 13:28:09 <elvispre> No vendor partition.
Jul 29 13:28:51 <elvispre> I took quite a lot of trouble to note down the partion layout "out-of-the-box", so I can answer these with some confidence.
Jul 29 13:29:15 <saidinesh5> Ahh
Jul 29 13:29:27 <saidinesh5> so could it be that your lineageOS build is from a treble layout?
Jul 29 13:29:49 <elvispre> ...in which case, it should say so :-)
Jul 29 13:30:16 <saidinesh5> heh well let's hope you figure this out and then can happily update the wiki
Jul 29 13:30:23 <elvispre> Or fail to install with a useful error message.
Jul 29 13:30:30 <saidinesh5> https://forum.xda-developers.com/mi-a1/development/dev-project-treble-conversion-t3790479
Jul 29 13:30:32 <elvispre> :-)
Jul 29 13:32:27 <saidinesh5> btw. how long did it take you guys to get the bootloader unlock thing?
Jul 29 13:33:22 <elvispre> android one does not require any codes. fastboot oem unlock Just Works straightaway.
Jul 29 13:33:43 <elvispre> Have to enable dev options, etc of course.
Jul 29 13:34:30 <saidinesh5> Ahh interesting
Jul 29 13:34:40 <saidinesh5> the original xioami devices make you jump through N hoops
Jul 29 13:34:46 <saidinesh5> crazy N hoops
Jul 29 13:35:02 <saidinesh5> how do i make make setup-webos-ports run again?
Jul 29 13:35:04 <elvispre> Tofe knows about that, I think
Jul 29 13:35:09 <saidinesh5> the topdir is currently wrong
Jul 29 13:35:21 <saidinesh5> (i am now inside a chroot
Jul 29 13:35:31 <saidinesh5> (and topdir changed)
Jul 29 13:35:57 <elvispre> webos-ports keeps going down today.
Jul 29 13:36:10 <saidinesh5> oh
Jul 29 13:36:11 <elvispre> Can you inspect the Makefile
Jul 29 13:36:37 <elvispre> Oh, you probably don't have it yet!
Jul 29 13:36:45 <saidinesh5> i do have the make file
Jul 29 13:36:48 <saidinesh5> i just tried make update
Jul 29 13:36:50 <saidinesh5> lets see
Jul 29 13:37:33 <elvispre> OK. make update then cd into webos-ports, . setup-env then do your build.
Jul 29 13:38:25 <saidinesh5> nah still the same error
Jul 29 13:38:39 <elvispre> what error?
Jul 29 13:38:48 <saidinesh5> topdir doesn't exist
Jul 29 13:39:06 <elvispre> Hmm. That's not so good :-)
Jul 29 13:39:15 <saidinesh5> because the drive is now mounted to another place and topdir.conf poitns to the old one
Jul 29 13:39:26 <saidinesh5> yeah wanted to make sure all the files are properly updated instead of just updating topdir
Jul 29 13:41:33 <elvispre> take a look in conf/topdir.conf?
Jul 29 13:41:45 <saidinesh5> yep. that was pointing to my old topdir
Jul 29 13:51:50 <saidinesh5> looked at the makefile once more
Jul 29 13:52:01 <saidinesh5> i think just removing the conf file will work
Jul 29 13:52:25 <saidinesh5> although you guys need a make force-update or make cleanconf
Jul 29 13:55:32 <saidinesh5> hmm...
Jul 29 13:55:53 <saidinesh5>   Error, TMPDIR has changed location. You need to either move it back  or rebuild
Jul 29 13:57:46 <saidinesh5> out of curiosity
Jul 29 13:57:52 <saidinesh5> if i remove tmp-glibc
Jul 29 13:57:57 <saidinesh5> will it even cause redownload?
Jul 29 14:08:35 <saidinesh5> elvispre: ?
Jul 29 14:17:08 <saidinesh5> wow
Jul 29 14:17:14 <saidinesh5> just du -s is taking forever there
Jul 29 14:21:05 <saidinesh5> oh well
Jul 29 14:21:10 <saidinesh5> just bind mounted it again to the path
Jul 29 14:21:24 <saidinesh5> and continuing
Jul 29 14:21:29 <saidinesh5> or rather hoping to continue
Jul 29 14:27:38 <saidinesh5> Tofe: reagarding your problem with anbox/init thing
Jul 29 14:28:14 <saidinesh5> i don't think it is a good idea to commit out exit() there
Jul 29 14:28:30 <saidinesh5> iirc there was another patch to use a different location for the property service
Jul 29 14:29:22 <saidinesh5> you also had to patch bionic for that though iirc
Jul 29 14:33:24 <saidinesh5> there was also a neutered init: https://github.com/saidinesh5/init , but ifyou use this, i am pretty sure you will get bittenby the change in properties inside the container affecting the properties outside the container
Jul 29 14:34:22 <saidinesh5> the original idea was to run android inside a chroot .. but you would need binder namespace and some other namespace for it anyway
Jul 29 14:34:41 <saidinesh5> bah
Jul 29 14:34:43 <saidinesh5> copy("layout_test_data_mojo_bindings") {
Jul 29 14:35:28 <saidinesh5> screw it
Jul 29 14:35:31 <saidinesh5> starting a full rebuild
Jul 29 14:35:33 <saidinesh5> removing tmp-glibc
Jul 29 16:34:04 <saidinesh5> hmm.. ERROR: Task (/src/LuneOS/webos-ports-env/webos-ports/meta-webos-ports/meta-luneos/recipes-webos/nyx-modules/nyx-modules.bb:do_configure) failed with exit code '1'
Jul 29 16:35:21 <saidinesh5> | -- Checking for module 'libudev'
Jul 29 16:35:22 <saidinesh5> | --   No package 'libudev' found
Jul 29 16:35:22 <saidinesh5> | CMake Error at /src/LuneOS/webos-ports-env/webos-ports/tmp-glibc/work/qemux86-webos-linux/nyx-modules/6.1.0-94+gitAUTOINC+362b2bde9a-r0/recipe-sysroot-native/usr/share/cmake-3.7/Modules/FindPkgConfig.cmake:415 (message):
Jul 29 16:37:39 <saidinesh5> bah
Jul 29 16:37:40 <saidinesh5> ERROR: Task (/src/LuneOS/webos-ports-env/webos-ports/meta-qt5/recipes-qt/qt5/qtwebengine_git.bb:do_install) failed with exit code '1'
Jul 29 16:37:45 <saidinesh5> what craziness is this
Jul 29 16:39:25 <elvispre|s> Have you run out of disk space, maybe?
Jul 29 16:45:54 * saidinesh5 checks
Jul 29 16:46:14 <saidinesh5> 160GB free elvispre
Jul 29 16:46:35 <saidinesh5> plus something wrong with nyx-modules recipe
Jul 29 16:46:52 <saidinesh5> it was looking for libudev that it didn't find
Jul 29 16:47:17 <saidinesh5> as for webengine: | sed: can't read /src/LuneOS/webos-ports-env/webos-ports/tmp-glibc/work/i586-webos-linux/qtwebengine/5.11.1+gitAUTOINC+fe73e54057_bad02200c6-r0/image/usr/lib/pkgconfig/Qt5WebEngineCore.pc: No such file or directory
Jul 29 17:31:40 <elvispre|s> saidinesh5: : My guess is you ran short of memory somewhere along the way. As I was saying, I had to buy more because my build machine tries to do so much at once. How many jobs does yours run at once and how much memory do you have?
Jul 29 17:32:33 <elvispre|s> The build errors I was getting with just 16 GB were similarly strange.
Jul 29 18:17:25 <saidinesh5> elvispre: activating 16GB of swap asap
Jul 29 18:17:44 <saidinesh5> although my 16GB ram had like 10 GB free when these errors happened
Jul 29 18:18:31 <saidinesh5> | /usr/include/features.h:367:25: fatal error: sys/cdefs.h: No such file or directory
Jul 29 18:18:33 <saidinesh5> wtf
Jul 29 18:18:55 <elvispre> That possibly means that should be a generated file and it was not generated.
Jul 29 18:19:06 <saidinesh5> yeah
Jul 29 18:19:30 <saidinesh5> even udev was missing
Jul 29 18:19:37 <saidinesh5> i think some packages need to be built first before this
Jul 29 18:20:41 <elvispre> I think the build does not notice all errors reliably.
Jul 29 18:21:13 <saidinesh5> libudev comes from which package?
Jul 29 18:21:15 <saidinesh5> systemd?
Jul 29 18:21:39 <elvispre> Not sure. Sounds likely though.
Jul 29 18:21:56 <saidinesh5> yeah the systemd monster gobbled it up a few years ago iirc
Jul 29 18:22:07 <elvispre> :-)
Jul 29 18:25:54 <saidinesh5> okay nyx-modules compiled
Jul 29 18:25:57 <saidinesh5> after i cleaned the cache
Jul 29 18:26:00 <saidinesh5> cleanall that is
Jul 29 18:26:11 <saidinesh5> and installed systemd first before that
Jul 29 18:31:37 * elvispre gives up. It is clearly not possible to install LineageOS on *this* Mi A1. Not even nearly possible.
Jul 29 18:31:58 <saidinesh5> feel free to send me that A1 :P
Jul 29 18:32:10 <saidinesh5> im liking bitbake so far though
Jul 29 18:32:13 <saidinesh5> almost intuitive
Jul 29 18:32:44 <elvispre> The whole Yocto build system is really impressive.
Jul 29 18:33:52 <saidinesh5> yeah .. way more responsive than android buildsystem .. or even the sailfish scripts..
Jul 29 18:34:13 <saidinesh5> and unlike those two , this one gives "did you mean listtasks?"
Jul 29 18:34:44 * elvispre gives up trying to install *LineageOS*, not LuneOS ;)
Jul 29 18:34:51 <saidinesh5> lol
Jul 29 18:35:04 <saidinesh5> can you even install the latter without the former though?
Jul 29 18:35:36 <saidinesh5> wouldnt you need the vendor blobs of the correct version - which come from Lineage OS?
Jul 29 18:35:56 <elvispre> Yes. Tofe's instructions will be credible and stand a chance of actually working.
Jul 29 18:36:38 <elvispre> The android one image ought to be a decent starting point already.
Jul 29 18:37:12 <saidinesh5> The Android One image has sources available?
Jul 29 18:37:56 <saidinesh5> iirc the AOSP paths etc.. were a little different from lineage paths etc.. and you couldnt blindly use the device/ of aosp with lineage builds
Jul 29 18:39:44 <elvispre> We have some work to do, but Tofe and Herrie have made a start. I was just trying LineageOS to build up some experience. I got some of that alright!
Jul 29 18:40:18 <saidinesh5> Ahh
Jul 29 20:53:36 <saidinesh5> Bahhh
Jul 29 20:53:57 <saidinesh5> looks like the qtwebengine error is not so crazy at all: https://git.yoctoproject.org/cgit.cgi/poky/plain/meta/recipes-core/musl/bsd-headers/sys-cdefs.h
Jul 29 22:16:18 <saidinesh5> https://bugreports.qt.io/browse/QTBUG-65004
Jul 29 22:16:21 <saidinesh5> actually here
**** ENDING LOGGING AT Mon Jul 30 03:00:00 2018