#nemomobile log for Wednesday, 2020-02-26

T42<starbuck2018> https://twitter.com/thepine64/status/123170249930589389101:51
T42<starbuck2018> So "maemoleste" is the "competitor" to nemo/sfos?01:51
*** verin0x2 is now known as verin0x03:52
T42<jgibbon> I'd call it cousin. Shares some dna, at least.05:38
T42<rhysday> what are the pros/cons of maemoleste over sfos? personal taste? and seems larger database of old n900 apps etc?05:38
T42<jgibbon> Bit off topic here, being neither a sfos nor a leste channel, but it's basically trying to get the hildon interface from the nokia n900 running with current software/devuan. No pro/con necessary, leste is pretty experimental (which is awesome, don't get me wrong).05:47
T42<neochapay> https://gitlab.com/nemomobile07:06
T42<neochapay> Why qt build on arm fail https://build.merproject.org/package/live_build_log/home:neochapay:mer:qt/qtbase/latest_armv7hl/armv8el but 486 build fine14:11
T42<starbuck2018> failed on arm64?14:23
T42<neochapay> No armv814:33
PureTryOut[m]<T42 "<neochapay> https://gitlab.com/n"> Oh, moving to Gitlab from Github? Me like14:39
T42<neochapay> It just for packages who not updated by jolla14:40
PureTryOut[m]Ah Qt 5.12.x vs 5.6.x then14:41
PureTryOut[m]Btw on pmOS we have calling and SMS working with Plasma Mobile. You might look into our package to see how to make it work on Nemo Mobile as well14:41
PureTryOut[m](for the PinePhone)14:41
T42徐志掎 %lastname% was added by: 徐志掎 %lastname%14:55
rinigusneochapay: I'm away from pc, so cannot check logs for your case. For me, arm 32 bit was failing due to qemu bugs (flatpak qt 5.12 and 5.14 apps). Will try to find relevant issues when will get an opportunity15:08
T42<neochapay> ```[  277s] Cannot read /home/abuild/rpmbuild/BUILD/qt5-5.12.7+master.20200226153128.1.g42cfa11/upstream/mkspecs/qmake.conf: No such file or directory15:38
T42<neochapay> [  277s] Could not read qmake configuration file /home/abuild/rpmbuild/BUILD/qt5-5.12.7+master.20200226153128.1.g42cfa11/upstream/mkspecs/qmake.conf.15:38
T42<neochapay> [  277s] Error processing project file: /home/abuild/rpmbuild/BUILD/qt5-5.12.7+master.20200226153128.1.g42cfa11/upstream/qtbase.pro15:38
T42<neochapay> [  277s] error: Bad exit status from /var/tmp/rpm-tmp.fHMLo0 (%build)```15:38
T42<neochapay> but on i486 all is well15:38
T42<neochapay> ```./configure --disable-static -confirm-license -platform linux-g++ -prefix /usr -bindir /usr/lib/qt5/bin -libdir /usr/lib -docdir /usr/share/doc/qt5/ -headerdir /usr/include/qt5 -datadir /usr/share/qt5 -plugindir /usr/lib/qt5/plugins -importdir /usr/lib/qt5/imports -translationdir /usr/share/qt5/translations -sysconfdir /etc/xdg -15:43
T42examplesdir /usr/lib/qt5/examples -archdatadir /usr/share/qt5 -testsdir /usr/lib/qt5/tests -qmldir /usr/lib/qt5/qml -libexecdir /usr/lib/qt5/libexec -opensource -no-sql-ibase -no-sql-mysql -no-sql-odbc -no-sql-psql -plugin-sql-sqlite -no-sql-sqlite2 -no-sql-tds -system-sqlite -system-zlib -system-libpng -system-libjpeg -no-rpath -optimized-qmake -d15:43
T42bus-linked -no-strip -no-separate-debug-info -verbose -opengl es2 -no-opengles3 -no-openvg -nomake tests -nomake examples -no-xkbcommon -no-xcb -qreal float -journald 'QMAKE_CFLAGS_RELEASE=-O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -Wformat -Wformat-security -fmessage-length=0 -march=armv7-a15:43
T42-mfloat-abi=hard -mfpu=neon -mthumb -Wno-psabi -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -Wformat -Wformat-security -fmessage-length=0 -march=armv7-a -mfloat-abi=hard -mfpu=neon -mthumb -Wno-psabi' 'QMAKE_CXXFLAGS_RELEASE=-O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protec15:43
T42tor --param=ssp-buffer-size=4 -Wformat -Wformat-security -fmessage-length=0 -march=armv7-a -mfloat-abi=hard -mfpu=neon -mthumb -Wno-psabi -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -Wformat -Wformat-security -fmessage-length=0 -march=armv7-a -mfloat-abi=hard -mfpu=neon -mthumb -Wno-psabi'```15:43
T42<neochapay> config options15:43
PureTryOut[m]Ok can this Telegram <-> IRC bridge replaced for something better, possibly through Matrix? That above code block looks waaayyyyy too ugly15:46
T42<neochapay> https://pastebin.com/58dc7pqu error message15:48
T42<neochapay> https://pastebin.com/FjHS13Pm config options15:48
PureTryOut[m]Even if you post it in pastebins, I would still like this bridge replaced by something more integrated. Posting everything through a relay bot is just really ugly and now both Matrix and Telegram miss out on each others formatting15:54
T42<jmlich> By the way, is mer/nemo affected by issue with lcd voltage? https://gitlab.com/postmarketOS/pmaports/-/merge_requests/99416:09
T42aa13q was added by: aa13q16:15
T42<aa13q> 816:15
PureTryOut[m]jmlich: if it hasn't updated the kernel to a version including the change, then yes16:17
rinigusneochapay: see list of issues that I encountered while working with flatpak arm and cross-compiling it:  https://github.com/sailfishos-flatpak/main/blob/master/AppDevelopment.md#known-issues19:05
rinigusI hope yours is different as there is no great solution so far... Although,  not finding file sounds like missing statx issue I have19:06
rinigusMaybe we can patch qmake to skip that call and see if it helps19:07
T42<starbuck2018> Is flatpak a requirement?19:22
rinigusNot at all, but cross-compiling is probably needed in direction x86_64 -> arm 32 bit19:25
rinigusBtw, aarch64 worked for me way better (cross-compiling to aarch64 )19:26
rinigusFlathub is using aarch64 servers which also avoids issues when compiling for arm 3219:27
T42<neochapay> maybe export CROSS_COMPILE will help......20:23
T42<neochapay> or correct QMAKE_CFLAGS20:24
rinigusNeoChapay: if my guess is right, we need to patch qfilesystemengine as described in https://bugs.kde.org/show_bug.cgi?id=416262#c821:29
merbotKDE bug 416262 in general "KDE Flatpak 5.12 Sdk broken in ARM" [Normal,Reopened]21:29
rinigusor what about using aarch64? can you try to compile with that arch at obs? (not sure whether we have it there, but I have a feeling you worked on it as well)21:30

Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!