[kde-freebsd] building KDE4 on CURRENT r255948 ports r328930 still fails

Schaich Alonso alonsoschaich at fastmail.fm
Tue Oct 8 19:44:17 UTC 2013


On Tue, 8 Oct 2013 19:33:36 +0200
Tijl Coosemans <tijl at coosemans.org> wrote:

> On Tue, 8 Oct 2013 15:59:01 +0200 Matthias Apitz wrote:
> > I have always a core file in $HOME after starting KDE4; a gdb bt is:
> > 
> > # gdb /usr/local/kde4/bin/kactivitymanagerd kactivitymanagerd.core
> > ...
> > [New Thread 2c403080 (LWP 100158/kactivitymanagerd)]
> > (gdb) bt
> > #0  0x00000000 in ?? ()
> > #1  0x2a20e10e in __dynamic_cast (src_ptr=0x2c40dc20,
> > #src_type=0x28458bc0, dst_type=0x28458c10, src2dst=0)
> >     at ../../.././../gcc-4.6.3/libstdc++-v3/libsupc++/dyncast.cc:61
> 
> This is probably because kdelibs was compiled with clang/libc++ and
> kactivitymanagerd was compiled with gcc/libstdc++.  Mixing C++
> runtime libraries like that doesn't work.
> 
> In x11/kactivitymanagerd/Makefile see if commenting out USE_GCC=yes
> and then rebuilding the port helps.

Is this ports or area51?

IIRC clang can build kactivitymanagerd, but the built binary will not work,
or something like that. Also, kactivitymanagerd needs GCC 4.8 which was in
beta state back than, not 4.6. There was a mail exchange on this issue half a
year or so ago on this mailing list, though I can't find it right now.

Alonso


More information about the kde-freebsd mailing list