Using KDE-PIM docker container

[Daniel Vrátil]

On Thursday, April 4, 2019 7:30:47 PM CEST David Jarvie wrote:
> On Thursday 04 Apr 2019 00:15:32 David Jarvie wrote:
> > On Wednesday 03 Apr 2019 19:04:32 David Jarvie wrote:
> > > On Tuesday 02 Apr 2019 15:28:14 Daniel Vrátil wrote:
> > > > On Tuesday, April 2, 2019 11:00:49 AM CEST Daniel Vrátil wrote:
> > > > > Hi David,
> > > > > 
> > > > > On Monday, April 1, 2019 7:51:58 PM CEST David Jarvie wrote:
> > > > > > Does the KDE PIM docker container setup described in
> > > > > > https://community.kde.org/KDE_PIM/Docker still work? The version
> > > > > > of
> > > > > > frameworks which is installed in it is 5.50, which is too old for
> > > > > > Applications 19.04. When I try to build frameworks in this
> > > > > > container,
> > > > > > there
> > > > > > are errors due to the Ubuntu version (xenial) used being too old.
> > > > > > Frameworks (kwallet) now requires libgpgmepp-dev, but this only
> > > > > > became
> > > > > > available in Ubuntu bionic.
> > > > > 
> > > > > Hmm, I haven't used it in a while, something needs updating I
> > > > > suppose.
> > > > > 
> > > > > > Perhaps /etc/apt/sources.list is out of date - it is is set up for
> > > > > > a
> > > > > > xenial
> > > > > > system. Not sure what the latest Neon uses, or how to update to
> > > > > > that
> > > > > > while
> > > > > > using the KDE PIM docker setup.
> > > > > 
> > > > > Looks like Neon changed the image tags, so we use an outdated
> > > > > "dev-stable"
> > > > > image, while we should be using "unstable" or "testing".
> > > > > 
> > > > > I'll look into it.
> > > > 
> > > > I've updated the Dockerfile now and successfully built KDE PIM the
> > > > container. Try it now and let me know if there are any issues :)
> > > 
> > > Hi Dan,
> > > 
> > > Thanks very much for that update. It seems to pull in the right packages
> > > now, and at least some of kdepim now builds ok.
> > > 
> > > However, there is a rather strange error building the akonadi module,
> > > which
> > > I wonder if you have any ideas about:
> > > 
> > > [  0%] Generating Protocol implementation
> > > ../../bin/protocolgen: error while loading shared libraries:
> > > libQt5Core.so.5: cannot open shared object file: No such file or
> > > directory
> > > src/private/CMakeFiles/generate_protocol.dir/build.make:61: recipe for
> > > target 'src/private/protocol_gen.cpp' failed
> > > make[2]: *** [src/private/protocol_gen.cpp] Error 127
> > > CMakeFiles/Makefile2:1677: recipe for target
> > > 'src/private/CMakeFiles/generate_protocol.dir/all' failed
> > > 
> > > The file /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 does exist on the
> > > system.>
> > > 
> > > Running 'ldd akonadi/bin/protocolgen' shows the following:
> > >         linux-vdso.so.1 (0x00007ffff0bd0000)
> > >         libQt5Core.so.5 => not found
> > >         libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6
> > > 
> > > (0x00007f2cfd1ae000)
> > > 
> > >         libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1
> > > 
> > > (0x00007f2cfcf96000)
> > > 
> > >         libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6
> > >         (0x00007f2cfcba5000)
> > >         libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6
> > >         (0x00007f2cfc807000)
> > >         /lib64/ld-linux-x86-64.so.2 (0x00007f2cfd761000)
> > > 
> > > So it has found libstdc++.so.6 in the same directory that
> > > libQt5Core.so.5
> > > is in, but for some reason it doesn't find libQt5Core.so.5. [Note that
> > > libQt5Core.so.5 is a link to libQt5Core.so.5.12.0, which also does
> > > exist.]
> > > 
> > > I attach the full build output with VERBOSE=1 set.
> > 
> > I got the same error trying to build kdiagram as part of the kdepim build.
> > So it looks like a general setup problem in the container rather than
> > something particular to akonadi.
> 
> It looks as if the issue is because Qt 5.12 is incompatible with my kernel,
> which is quite old now (3.16). So I may have to go to a full Neon
> installation in a virtual machine in order to build Applications 19.04.

Weird - I'm not sure how those two things would be related (unless it's some 
Docker thing). I've built the image from scratch and ran "kdesrc-build kde-
pim" in the container, all worked just fine. I havent' tried running anything.

Could your external environment settings somehow leak into the container, 
changing LD_LIBRARY_PATH or something like that?

- Dan


-- 
Daniel Vrátil
www.dvratil.cz | dvratil at kde.org
IRC: dvratil on Freenode (#kde, #kontact, #akonadi, #fedora-kde)

GPG Key: 0x4D69557AECB13683
Fingerprint: 0ABD FA55 A4E6 BEA9 9A83 EA97 4D69 557A ECB1 3683
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-pim/attachments/20190405/60733f5d/attachment.sig>