**** BEGIN LOGGING AT Sat Dec 22 03:00:03 2018
Dec 22 08:09:24 <ubptgbot> <Daniel> Hi, I have been able to resolve some of my former issues. The android contrainer is now launched correctly. I am on a x86  system (not ARM) using @ilyaishere s rootfs. … "dpkg —print-architecture" gives me "i386" but "arch" results in "i686"  … But when trying to start kwin_wayland, the system complains about not finding libQt5Core.s
Dec 22 08:09:24 <ubptgbot> o.5 … According to strace the system tries to find the i686 version of these files, but only the i386 files exist. … Any suggestions? Any way to force the system using the i386 libs instead? … Thanks for any input... … strace: https://paste.ubuntu.com/p/TgqV7FYBCp/
Dec 22 08:11:04 <ubptgbot> <ilyaishere> @Daniel, Hello! There's no real difference between i386 and i686
Dec 22 08:11:45 <ubptgbot> <ilyaishere> What I think you're facing is that the newer versions of Qt Core have a kernel version dependency
Dec 22 08:12:17 <ubptgbot> <ilyaishere> (so the linker skips the unsupported library)
Dec 22 08:13:43 <ubptgbot> <Daniel> Oh, that might be the case as I am stuck on 3.10. I'll look into this, thanks for the input.
Dec 22 08:13:52 <ubptgbot> <ilyaishere> *tries to find the messages*
Dec 22 08:16:56 <ubptgbot> <Daniel> "Qt 5.10 started using the getrandom(2) syscall which was introduced in Linux 3.17" - damn what do I do now? Can I downgrad the libraries?
Dec 22 08:16:58 <ubptgbot> <ilyaishere> (Photo, 1183x688) https://irc.ubports.com/jRR1XOxn.png
Dec 22 08:16:58 <ubptgbot> <ilyaishere> Fwd from ilyaishere: Ok, I guess OS ABI is the issue
Dec 22 08:16:58 <ubptgbot> <ilyaishere> Fwd from ilyaishere: It says 3.17
Dec 22 08:16:59 <ubptgbot> <ilyaishere> Fwd from JBBgameich: Since  renameat2 and getentropy seem to have fallbacks, can we just disable them for now? It's not nice having to fork the Qt packaging for all devices now, but it seems to be the easiest solution right now.
Dec 22 08:16:59 <ubptgbot> <ilyaishere> Fwd from ilyaishere: We have to disable it
Dec 22 08:16:59 <ubptgbot> <ilyaishere> Fwd from ilyaishere: What I'm trying to figure out is if the cmdline option is enough
Dec 22 08:17:00 <ubptgbot> <ilyaishere> Fwd from ilyaishere: Look at this line: http://code.qt.io/cgit/qt/qtbase.git/tree/src/corelib/io/qfilesystemengine_unix.cpp#n109
Dec 22 08:17:00 <ubptgbot> <ilyaishere> Fwd from ilyaishere: It seems like they enable it anyway if host kernel supports it
Dec 22 08:17:00 <ubptgbot> <ilyaishere> Fwd from ilyaishere: ```- Qt uses the statx(2) system call for obtaining file information on …    kernels 4.12 and later. Some older container systems install system call …    protection rules that do not include this system call. If you experience …    problems running Qt applications inside containers (such as the report
Dec 22 08:17:00 <ubptgbot> of …    a file not existing when it does), ensure the statx(2) is allowed in the …    container configuration.```
Dec 22 08:17:01 <ubptgbot> <ilyaishere> Fwd from ilyaishere: Undefined it, just in case...
Dec 22 08:17:01 <ubptgbot> <ilyaishere> Fwd from ilyaishere: Qt fixed
Dec 22 08:17:40 <ubptgbot> <bhushanshah> This is fixed in Qt 5.11.3+ FYI
Dec 22 08:17:57 <ubptgbot> <ilyaishere> @bhushanshah, But... How?
Dec 22 08:18:05 <ubptgbot> <ilyaishere> Our packaging?
Dec 22 08:19:02 <ubptgbot> <bhushanshah> https://packaging.neon.kde.org/qt/qtbase.git/tree/debian/patches/qt_syscall.diff?h=Neon/release upstream patch
Dec 22 08:19:15 <ubptgbot> <bhushanshah> (this was backported to 5.11.2 for neon)
Dec 22 08:21:06 <ubptgbot> <ilyaishere> @bhushanshah, Ah, and Daniel uses an x86 rootfs
Dec 22 08:21:10 <ubptgbot> <ilyaishere> Which is Debian
Dec 22 08:21:31 <ubptgbot> <bhushanshah> I think @JBBgameich also backported this... Correct?
Dec 22 15:34:15 <ubptgbot> <JBBgameich> I backported the patch recently, but due to some problems with the gitlab runners I'm not sure whether the package has already been built.
Dec 22 15:36:26 <ubptgbot> <JBBgameich> Just restarted the build, it might take a few hours to finish unfortunately.
Dec 22 15:37:24 <ubptgbot> <JBBgameich> https://gitlab.com/debian-pm/qtbase/blob/master/debian/patches/Stop-using-syscall-for-statx-and-renameat2.patch
Dec 22 15:40:23 <ubptgbot> <JBBgameich> @Daniel, Is the rootfs you are using up to date or a few weeks / month old? … There are some weekly builds here: https://archive.kaidan.im/debian-pm/images/debian-halium-plamo-buster-armhf.tar.xz … (They are mostly untested, but might be worth trying.) … Once the qt build has finished, you probably need to upgrade.
Dec 22 15:40:29 <ubptgbot> <JBBgameich> @Daniel, [Edit] Is the rootfs you are using up to date or a few weeks / month old? … There are some weekly builds here: https://archive.kaidan.im/debian-pm/images/debian-halium-plamo-buster-armhf.tar.xz … (They are mostly untested, but might be worth trying.) … Once the qt build has finished, you probably need to upgrade th
Dec 22 15:40:29 <ubptgbot> e rootfs using apt.
Dec 22 15:44:35 <ubptgbot> <ilyaishere> @JBBgameich, He uses builds from that place, but x86
Dec 22 15:52:19 <ubptgbot> <JBBgameich> Okay, cool. … I'm really looking forward to dropping the forked Qt packages, although I'm not sure if this will ever happen. arm64 is going to become an gles architecture in debian afaik, but I386 is unlikely to become one.
Dec 22 16:21:55 <ubptgbot> <UniversalSuperBox> I still haven't forgotten about your cloud builder @JBBgameich... Scaleway is being a jerk
Dec 22 16:42:09 <ubptgbot> <Daniel> I have also tried the build 12/20/2018 resulting in the same error (libQtCore no such file). I‘ll try the new build once it has finished building and post results here. Thanks very much for the support and the effort!
**** ENDING LOGGING AT Sat Dec 22 18:13:38 2018

**** BEGIN LOGGING AT Sat Dec 22 18:17:07 2018
Dec 22 20:52:43 <ubptgbot> <JBBgameich> I'm just building Qt on my local machine right now, since the I386 runner is somehow not working currently.
Dec 22 20:53:12 <ubptgbot> <JBBgameich> And the log is too long to show the actual problem
Dec 22 21:09:26 <ubptgbot> <RavengamerSpace> Hi everyone ! … If I'm here it's because I want to port UBports to my Huawei's phone. … So do you way or tips to share to me ? … I know there is a documentation. But I found it not very precise
Dec 22 21:09:41 <ubptgbot> <UniversalSuperBox> What are you missing?
Dec 22 21:10:25 <ubptgbot> <RavengamerSpace> Well, in fact I haven't build ROM yet but I wanted to learn
Dec 22 21:12:04 <ubptgbot> <UniversalSuperBox> Oh. There should be enough information there to get you through it. Just ask here if you have any questions for us.
Dec 22 21:13:04 <ubptgbot> <RavengamerSpace> Okay, thanks a lot … I would be the most happy guy if I successfully port UBports on my phone
Dec 22 21:17:40 <ubptgbot> <RavengamerSpace> So now, I wait the synchronization of the git on my computer … (Luckily, I had a decent connection)
Dec 22 22:35:20 <ubptgbot> <Daniel> @JBBgameich, Ok, thanks. I am really excited if it'll be running on my 3.10 kernel.
Dec 22 23:46:15 <ubptgbot> <JBBgameich> Well, it should. All the neccesary changes should be there. The build has finished, but it's not yet imported Into the repo. I hope the cron job isn't somehow broken :/
Dec 22 23:51:03 <None4U> when I run mkbootimg
Dec 22 23:51:04 <None4U> https://pastebin.com/4yFNrEeA
Dec 22 23:52:46 <ubptgbot> <UniversalSuperBox> It says the problem is a missing `endif`. Did you comment out an `endif` in that file
Dec 22 23:53:35 <None4U> didn't touch it
Dec 22 23:53:37 <None4U> it's from los
Dec 22 23:54:00 <ubptgbot> <UniversalSuperBox> Did you comment out an endif somewhere else
Dec 22 23:54:11 <ubptgbot> <UniversalSuperBox> It could be in an import in that place in the file too
Dec 22 23:56:35 <None4U> hmm
Dec 22 23:56:36 <None4U> https://pastebin.com/P0YJVfEq
Dec 22 23:56:37 <None4U> odd
Dec 22 23:56:41 <None4U> why is it empty
Dec 22 23:57:01 <ubptgbot> <UniversalSuperBox> Well, it is definitely missing an endif
Dec 22 23:57:27 <None4U> why is it missing everything
Dec 22 23:58:30 <None4U> uhh
Dec 22 23:58:40 <ubptgbot> <UniversalSuperBox> I'm not sure. Is there anything in that file in upstream source?
Dec 22 23:58:41 <None4U> could you keep messaging?
Dec 22 23:58:49 <None4U> los?
Dec 22 23:58:58 <None4U> OK, I have to leave
Dec 23 00:32:35 <None4U> umm
Dec 23 00:32:39 <None4U> I am assuming los
Dec 23 00:33:05 <ubptgbot> <UniversalSuperBox> Yes, but you said you had to leave
Dec 23 00:33:51 <None4U> but los doesn't have said file
Dec 23 00:33:54 <None4U> https://github.com/LineageOS/android_device_samsung_jfltexx
Dec 23 00:34:06 <ubptgbot> <UniversalSuperBox> Ehm... where did it come from then?
Dec 23 00:35:15 <None4U> dunno
Dec 23 00:35:25 <ubptgbot> <UniversalSuperBox> What repo did you pick?
Dec 23 00:35:30 <ubptgbot> <UniversalSuperBox> To use these files from
Dec 23 00:35:41 <None4U> want to see my manifest?
Dec 23 00:35:45 <ubptgbot> <UniversalSuperBox> Sure
Dec 23 00:37:25 <None4U> https://pastebin.com/CYz46eR6
Dec 23 00:38:00 <ubptgbot> <UniversalSuperBox> Did you look at the right branch in the upstream repository?
Dec 23 00:38:25 <None4U> it isn't los
Dec 23 00:38:31 <None4U> that's in a different place
Dec 23 00:38:42 <ubptgbot> <UniversalSuperBox> Erm... yeah it is
Dec 23 00:38:50 <None4U> where is the "vendor" folder come from?
Dec 23 00:38:57 <None4U> *does
Dec 23 00:39:12 <ubptgbot> <UniversalSuperBox> https://github.com/themuppets/proprietary_vendor_samsung
Dec 23 00:39:44 <None4U> cool
Dec 23 00:40:00 <None4U> well I looked there but I didn
Dec 23 00:40:01 <None4U> 't
Dec 23 00:40:03 <None4U> know
Dec 23 00:40:21 <None4U> and there is no jfltexx
Dec 23 00:40:55 <None4U> or lineage 7.1
Dec 23 00:41:01 <None4U> er
Dec 23 00:41:02 <None4U> 17
Dec 23 00:41:07 <None4U> is it 16?
Dec 23 00:41:14 <ubptgbot> <UniversalSuperBox> 15.1
Dec 23 00:41:19 <None4U> ok
Dec 23 00:41:24 <ubptgbot> <UniversalSuperBox> Wait, no sorry
Dec 23 00:41:25 <ubptgbot> <UniversalSuperBox> 14.1
Dec 23 00:41:31 <None4U> yup
Dec 23 00:41:58 <None4U> well there still isn't jfltexx
Dec 23 00:42:07 <ubptgbot> <UniversalSuperBox> Who made this manifest?
Dec 23 00:42:13 <None4U> https://github.com/Halium/projectmanagement/issues/59
Dec 23 00:42:24 <None4U> but they got past this step
Dec 23 00:42:39 <ubptgbot> <UniversalSuperBox> I'm not sure they did
Dec 23 00:42:44 <ubptgbot> <UniversalSuperBox> "I'm stuck on mka halium-boot"
Dec 23 00:42:46 <None4U> it says
Dec 23 00:42:49 <None4U> yeah
Dec 23 00:42:55 <None4U> I am stuck on mkbootimg
Dec 23 00:43:03 <ubptgbot> <UniversalSuperBox> Add an ifdef
Dec 23 00:43:16 <None4U> ?
Dec 23 00:44:04 <None4U> what does that mean
Dec 23 00:44:37 <ubptgbot> <UniversalSuperBox> Er, endif
Dec 23 00:46:24 <ubptgbot> <UniversalSuperBox> Oh, there are jflte's in there.
Dec 23 00:46:45 <None4U> cool
Dec 23 00:46:46 <None4U> works now
Dec 23 00:46:48 <None4U> thanks
Dec 23 00:46:50 <ubptgbot> <UniversalSuperBox> There are separate ones for different carriers
Dec 23 00:47:11 <None4U> and I got a i9505
Dec 23 00:47:30 <ubptgbot> <UniversalSuperBox> There's an i9500 in there
Dec 23 00:47:37 <ubptgbot> <UniversalSuperBox> I assume the last one is for different regions
Dec 23 00:52:04 <None4U> https://pastebin.com/84CteScA
Dec 23 00:52:09 <None4U> OK I need to go now
Dec 23 00:52:16 <None4U> goodbye
**** ENDING LOGGING AT Sun Dec 23 03:00:00 2018