Sunday, 2021-04-11

*** zbenjamin_ is now known as zbenjamin01:33
*** frinring_ is now known as frinring01:46
deloptesHi, someone knows how to install kf5calendarcore in the SDK?10:38
deloptesSDK vers=
rinigusI have trouble with using bison. Always getting errors "bison: m4 subprocess failed: No such file or directory"13:37
rinigusSDK target 4.0.113:37
Nico[m]No m4 installed?13:37
rinigusIt is13:42
rinigusNico: and for some reason it does work on OBS while it doesn't work on SDK @ PC13:44
Nico[m]Very weird13:45
Nico[m]Which file is missing?13:45
rinigusNico: now that's a problem - it doesn't say13:46
Nico[m]Yeah, it never does, huh?13:46
Nico[m]Stracing is probably difficult?13:46
rinigusfrom make? hmm, thanks - will try. let's see if I get to it that way13:48
malrinigus: can you link to the obs project?14:00
rinigussame issue was with collectd, but I cheated there and added parse .c14:13
rinigusso, n=214:13
malrinigus: hmm, in my devel target that built without issues14:23
malI can try in 4.0.1 also if needed14:23
rinigusmal: on PC?14:26
rinigusmal: please try with current SDK that we have access to14:26
malrinigus: yes, that was on my laptop using platform sdk14:29
rinigusmal: would be good to test with the released target.14:30
maltrying with 4.0.1 now14:32
rinigusmal: thanks14:32
malrinigus: built fine also in target14:35
malfresh clone of the sources, with submodules synced also14:36
malrinigus: can you verify that submodules are synced in your local sources?14:36
rinigusmal: will try again with the fresh clone. was it out-of-tree build or within the src dir?14:37
maljust normal mb2 build14:37
rinigusdon't think it matters, but I will try to reproduce it14:37
rinigusmal: thanks. will try again and report back14:37
rinigusmal: no luck. have tried with sfdk after making fresh clone - failed. made new fresh clone and it failed the same way with mb2. tried -j1 - no help. will try to reinstall SDK14:47
rinigusmal: fresh SDK install, fresh clone, still failed. even rebooted for a good measure - no help15:13
riniguswill have to look whether it works on some other PC or server15:13
malrinigus: hmm, wondering if some dependency is missing or something15:46
rinigusmal: testing now in platform sdk that I use for ports15:46
rinigusbut it would be odd if some dep is missing and it would compile fine on OBS15:47
rinigusplatform SDK was fine...15:47
rinigusmal: let's see if docker would help in my case15:48
malhmm, what is so different in app sdk15:49
malrinigus: I often build even apps in platform sdk15:49
rinigusmal: no idea why it trips. can only speculate at this point, but let's see if docker will help15:51
rinigusnope - docker tripped on the same spot15:52
rinigusmal: would take a break and think a bit. right now now idea how to approach it even. strace didn't help either, but can try again15:55
rinigusmal and Nico : strace helped, but had to read it right and run to follow forked processes. bison forks m4 while running. in SDK, bison runs under sb2 (was longish strace exec name with /srv/mer/targets/SailfishOS- while tries to fork /usr/bin/m416:59
rinigussomehow, m4 escaped sb2 and was run on host (docker main shell or vbox main env).17:00
rinigusas m4 was not installed there, it failed17:00
Nico[m]Maybe m4 is one of those whitelisted binaries?17:01
rinigusafter installing m4 and bison into the "host" env (docker and vbox main), all worked as expected)17:01
rinigusI presume, those are installed at OBS and platform SDK, but not for app SDK.17:02
rinigusso, for docker env, solution was to run `docker exec sailfish-os-build-engine zypper --non-interactive in bison`17:02
rinigusnotice absence of targets17:02
ol<rinigus "somehow, m4 escaped sb2 and was "> I remember this problem. It's not because of the way m4 is started, using posix_spawn() function that is not wrapped by sb2.17:16
ol> <> somehow, m4 escaped sb2 and was run on host (docker main shell or vbox main env).17:16
ol * I remember this problem. It's not because m4 is special, byt because of the way m4 is started, using posix_spawn() function that is not wrapped by sb2.17:16
ol * I remember this problem. It's not because m4 is special, but because of the way m4 is started, using posix_spawn() function that is not wrapped by sb2.17:16
ol(Not sure how message edits are shown on IRC side.)17:17
rinigusol: poor wording on my side. your explanation makes sense and maybe bison+m4 should be included into sdk by default17:17
olrinigus (IRC): It doesn't matter whether bison is included by default or not. If it uses posix_spawn(), the process started is not wrapped by sb2 anyway.17:19
rinigusol: it does. then it calls /usr/bin/m4 from host and if it is available build goes on just fine17:20
olThe way sb2 wraps file access and starting processes is very fragile. It's impossible to wrap only system calls using LD_PRELOAD magic. If all system calls were in a separate shared library (like in Windows), it would be possible. But glibc doesn't so it: fopen() and other higher level file access function are in the same library as open(), so all of these functions should be wrapped by preloaded library, and there are hundreds of them. And some of them are17:24
olimpossible to wrap correctly (like popen(), for example).17:24
Nico[m]<ol "(Not sure how message edits are "> horribly17:24
ol<Nico[m] "<ol "(Not sure how message edits"> I hope IRC will eventually die.17:25
olThere is no reason to keep using IRC when Matrix is superior in everything.17:29
Nico[m]<ol "<Nico[m] "<ol "(Not sure how mes"> He says on IRC from a Matrix server bridged to another Matrix server VIA IRC17:29
olAnd this is also a problem. I don't want to use bridge because I don't want to share my registered nick's password with a third party.17:31
olIf IRC bridges were smart enough to detect that Matrix user is bridged using another bridge, I would just bridge the same Matrix room using my own bridge just for me. But they are not, so this would lead to disastrous results.17:34
Nico[m]We just need to move this room to matrix and bridge it to IRC ;p17:35
Nico[m]So that matrix users don't need a nick pw17:35
olOr just move this room and don't bridge. So all remaining IRC users will switch to Matrix.17:36
Nico[m]That would be very rude17:37
olIt depends on what we want to achieve.17:37
Nico[m]I'm not on bord with forcing anything ;p17:38
olSome users don't even know about Matrix and how it's superior to IRC.17:38
attahAccessibility presumably?17:38
Nico[m]I mean, none ever made a good matrix client for Sailfish either!17:38
attahUntil then it seems a bit hypothetical...17:39
ol<Nico[m] "I mean, none ever made a good ma"> I don't want to point a finger.17:39
ol<attah "Accessibility presumably?"> Yes, including accessibility. Matrix is superior on this front as well.17:39
Nico[m]One day I will have the time to work on mine again .-.17:39
*** karmar281 is now known as karmar18:02
rinigusmal: next problematic package that fails on appSDK. It builds just fine on platformSDK as well as OBS.19:39
riniguserror while loading shared libraries: cannot open shared object file: No such file or directory19:39
rinigushowever, it is installed in the target as it is added to buildrequires19:40
rinigusmal: ^19:40
rinigushmm, and it build fine for aarch64 when using appSDK20:00
elros1rinigus not sure if its' any help for you but that libappstream-glib build fine using mb2 in application sdk (virtualbox) for armv7hl20:00
riniguselros1: looks like that issue is limited to i686 - target I use for faster checks20:01
rinigusthanks for checking20:01
elros1ah ok, I don't have i686 installed currently but if you want I coud check that also20:02
rinigusif you don't mind, please do. I used docker over here20:04
malrinigus: ah, could the same issue have been with the other package also, I used aarch64 target20:04
rinigusmal: no, ostree got fixed by adding bison / m4 into main env, as described above. after that, x86 target worked fine.20:06
rinigusalthough, I can't be sure20:06
rinigus... that I would get error if I would start from aarch6420:07
Thaodanrinigus: Is the tooling/target up to date? I remember fixing that.20:08
rinigusThaodan: wiped it and reinstalled it today. should be20:10
rinigusunless I need to install some EA version20:10
malsometimes people forget to update tooling (and also sdk itself) at least porters do20:12
rinigusmal: true, have done it as well. so legitimate question20:12
mal"sdk-foreach-su -ly zypper dup" is a nice thing (and other command you run the same way)20:14
malthat is how I update my devel targets20:15
elros1rinigus: I got warnings like:  (WARNING) ldd{bash}[4300]Executing statically linked native binary /srv/mer/targets/SailfishOS- but looks it also builds fine for i48620:16
riniguselros1: thanks! I have those warnings as well. no idea then why it failed over here20:18
rinigusmal: thanks - but my targets/tooling should be fine as they were installed today. although, handy command20:20
elros1here is full build log if you want to compare:
riniguselros1: thanks.20:22
rinigusit looks good20:22
rinigusas it is late, gn20:22

Generated by 2.17.1 by Marius Gedminas - find it at!