Using KDE-PIM docker container

[David Jarvie]

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.

-- 
David Jarvie.
KDE developer.
KAlarm author -- http://www.astrojar.org.uk/kalarm
-------------- next part --------------
A non-text attachment was scrubbed...
Name: build.log
Type: text/x-log
Size: 49050 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde-pim/attachments/20190403/d38927a9/attachment.bin>