**** BEGIN LOGGING AT Fri Dec 20 03:00:11 2019 Dec 20 09:24:03 Morning Dec 20 09:24:19 the guys were doing some work on all boxes last night & they got a reboot Dec 20 09:24:32 I can see bonaire is idle just now, but it seems to be available Dec 20 09:25:26 novaldex: OK thanks for the headsup. Any idea what happened or just random disk failure? Dec 20 09:27:09 little difficult to put into words, activity elsewhere on one of the networks meant the host that bonaire runs on lost it's connection to storage temporarily, but refused to find it again Dec 20 09:27:39 it was then being rather awkward in seeing it, even though it was there Dec 20 09:27:51 we've made some adjustments to itigate that happening again Dec 20 09:28:00 *mitigate Dec 20 09:45:52 novaldex: Thanks as always :) Dec 20 10:28:38 Hello, how can I port LuneOS to a device that has a Halium 7.1 port/ Dec 20 10:36:23 Hacker1245: Which device? Dec 20 10:36:44 Moto G5 (cedric) Dec 20 10:38:25 Morning! Dec 20 10:39:16 JaMa: I'm trying to build and rsync the last pinephone image to builds.webos-ports.org, but I get "ERROR: Unable to connect to bitbake server, or start one (server startup failures would be in bitbake-cookerdaemon.log)."... Dec 20 10:49:43 Hacker1245: YOu would need to fork meta-smartphone layer and add something similar as for Athene: https://github.com/shr-distribution/meta-smartphone/commit/9b92bdbbaa9d096717c190e709bca82e25d97207#diff-6f3dcc886e94fe5eb36716e43894dfe7 Dec 20 10:50:43 And the same for meta-webos-ports: https://github.com/webOS-ports/meta-webos-ports/commit/8f65ede9bda8f5b6f9a529893ae3b2791e269519#diff-4c3a5fae3a41d9286f5c3fa3e4568ad6 Dec 20 10:52:12 Then in general you can follow the build instructions as per: https://webos-ports.org/wiki/Build_for_Tenderloin Dec 20 10:52:21 Just replace tenderloin with cedric ;) Dec 20 10:52:59 Biggest issue you'll have is to get the kernel to build with new GCC usually Dec 20 10:53:10 You'll need some patches for that, depending on your kernel version Dec 20 10:54:03 Seeing it's a 3.18 kernel GCC fixes should be minimal though Dec 20 10:55:49 ToFe: let me see if bitbake is running.. Dec 20 11:01:00 Herrie: so fork both repos, modify the files to suit the device, then follow the build instruction? Dec 20 11:01:08 novaldex: thanks :) Dec 20 11:01:11 also clone both repos to my machine? Dec 20 11:02:34 Tofe: up & running again Dec 20 11:03:07 Hacker1245: yes, we do the builds locally, usually. Dec 20 11:03:49 alright, I'll message you if I need help Dec 20 11:04:06 novaldex: thanks! Dec 20 11:05:02 Tofe: welcome! Dec 20 11:16:48 Herrie: do I change this SRC_URI = "http://build.webos-ports.org/halium-luneos-7.1/halium-luneos-7.1-${PV}-${MACHINE}.tar.bz2" to something else in the android-system-image-athene.bb file? Dec 20 11:18:26 if I want to create android-system-image-cedric,bb Dec 20 11:26:13 Hacker1245: You would rename the file to cedric ;) Dec 20 11:26:24 This is the file that's generated by Halium 7.1 build basically Dec 20 11:26:31 We use the minimal steps there Dec 20 11:26:35 Oh so leave the url as is? Dec 20 11:27:25 Yes Dec 20 11:28:10 If you have the .tar.bz2 I can put it on above URL for you ;) Dec 20 11:28:26 Once there's a working port, we can add it to our Jenkins as a job to create it Dec 20 11:30:24 Herrie: Not yet as I'm creating files Dec 20 11:30:32 Hacker1245: Yeah I understand ;) Dec 20 11:30:48 This is our Halium build script that Jenkins runs. We only do small bits of whole Halium: https://github.com/webOS-ports/jenkins-jobs/blob/master/jenkins-job.sh#L554 Dec 20 11:32:04 We basically use up to "mka systemimage" from Halium docs: https://docs.halium.org/en/latest/porting/build-sources.html Dec 20 11:32:28 Afterwards we use the generated .tar.bz2 in our build. We build kernel with much newer GCC and fully integrated in our image for the rest Dec 20 11:33:17 Hence we have an image per device and not a generic rootfs like some others. Dec 20 11:35:08 Our defconfig is the same as Mer's/SFOS in general, so no fancy AppArmor tricks required Dec 20 11:41:32 can I use /dev/block/bootdevice/by-name/persist in fstab? Dec 20 11:41:43 or do I need the partition number? Dec 20 11:59:30 how do I create the udev rules? Dec 20 11:59:47 can I use the ones from UT? Dec 20 12:05:12 also do I use the cm 14.1 kernel or the Halium kernel source? Dec 20 13:10:28 Herrie: https://paste.ubuntu.com/p/88hy6gN86k/ got this after trying to build Dec 20 13:16:28 building on Ubuntu 16.04 x64 btw Dec 20 13:44:45 HAcker1245: udev rules you can use the UT ones I would say Dec 20 13:44:50 HAlium kernel better Dec 20 13:45:00 used the halium kernel Dec 20 13:45:03 Since that already should've run the Mer/SFOS kernel check Dec 20 13:45:08 but as I said the build errors out Dec 20 13:45:17 Can you paste full log? Dec 20 13:49:35 Ubuntu 16.04 x64 should be fine still. I'm on 18.04 myself but was on 16.04 before Dec 20 14:06:56 Herrie: gonna send the file via IRC Dec 20 14:11:53 could you accept it? Dec 20 14:12:40 since the file weighs 44 MB, tried to paste the whole log, couldn't Dec 20 14:13:40 Hacker1245: On my phone now, should be back at pc in 15-20 mins I guess Dec 20 14:13:44 Will ping you Dec 20 14:13:56 oh alright Dec 20 14:13:59 I'll wait **** BEGIN LOGGING AT Fri Dec 20 17:25:31 2019 Dec 20 17:35:31 Hacker1245: cross-localedef crashes... I've not seen that one before... Dec 20 17:35:48 limited the locales in config Dec 20 17:35:57 I'm checking if it builds Dec 20 17:55:43 The hell https://bpaste.net/show/TEC6K Dec 20 17:55:50 now boost is failing Dec 20 18:19:09 Hacker1245: that's really a lot of coredumps... are you running too many jobs in parallel? something else? Dec 20 18:19:34 I left the settings regarding threads unchanged Dec 20 18:21:27 I'm not sure what the default values are for these https://github.com/webOS-ports/webos-ports-setup/blob/master/conf/local.conf#L7 Dec 20 18:22:02 for me, I've setup 4 jobs and 4 parallel makes Dec 20 18:22:22 for I have a 4 cores cpu with 16GB ram only Dec 20 18:25:06 same here, 8GB of RAM though Dec 20 18:25:21 and it runs only 4 jobs Dec 20 18:33:10 8GB should work, I had that in my previous builder Dec 20 19:00:40 now boost passed... Dec 20 19:10:36 hmm Dec 20 19:10:38 | | ^~~ Dec 20 19:10:39 | /tmp/cc0e546r.s: Assembler messages: Dec 20 19:10:39 | /tmp/cc0e546r.s:1978: Error: .err encountered Dec 20 19:10:39 | /tmp/cc0e546r.s:2043: Error: .err encountered Dec 20 19:10:39 | /tmp/cc0e546r.s:2590: Error: .err encountered Dec 20 19:10:39 | /home/hello/luneos/webos-ports-env/webos-ports/tmp-glibc/work-shared/cedric/kernel-source/scripts/Makefile.build:257: recipe for target 'fs/fat/dir.o' failed Dec 20 19:10:42 | make[4]: *** [fs/fat/dir.o] Error 1 Dec 20 19:10:44 | /home/hello/luneos/webos-ports-env/webos-ports/tmp-glibc/work-shared/cedric/kernel-source/scripts/Makefile.build:402: recipe for target 'fs/fat' failed Dec 20 19:10:47 | make[3]: *** [fs/fat] Error 2 Dec 20 19:34:15 ideas how to resolve that? Dec 20 19:55:14 Try again? Dec 20 19:55:34 3.18 should work normally without patches for GCC I'd say Dec 20 19:55:53 well I'm getting that error consistently Dec 20 19:56:06 I might disable FAT Dec 20 19:59:22 did anyone else have this error? Dec 20 20:04:59 That one doesn't ring a bell Dec 20 20:05:55 want the kernel source link? Herrie Dec 20 20:08:11 Hacker1245: If you push what you have now, I can have a look tomorrow probably or the day after. Out now on X-mas bash with colleagues Dec 20 20:10:48 only push meta-motorola? Dec 20 20:11:23 Well meta-smartphone and meta-webos-ports Dec 20 20:11:31 alright Dec 20 20:16:49 https://github.com/Hacker1245/meta-motorola Dec 20 20:20:25 https://github.com/Hacker1245/meta-webos-ports Dec 20 20:22:55 I'll give it a go on my machine when I get a chance Dec 20 20:23:36 Got a Threadripper 2990wx with 128GB of RAM earlier this year, so can test things quickly there :) Dec 20 20:23:55 Just need to get access to it. Will be either tomorrow morning or evening I guess Dec 20 20:24:31 Will ping you or email you once I'm able to test Dec 20 20:25:44 better email me Dec 20 20:25:53 since I'm not always on IRC Dec 20 20:27:18 Ok Dec 20 20:27:33 Just want to make sure it's not your build system. Dec 20 20:27:47 Had some issues in the past which were due to my setup Dec 20 20:28:13 Once stuff builds it's usually pretty straight forward to get things booting :) Dec 20 21:08:10 I'd suspect the builder machine here, but it's just intuition, nothing solid **** ENDING LOGGING AT Sat Dec 21 02:59:58 2019