[kde-freebsd] Unable to build kdelibs (segmentation fault) or debug it

[Kevin Oberman]

On Wed, Mar 5, 2014 at 5:43 AM, Raphael Kubo da Costa <rakuco at freebsd.org>wrote:

> Kevin Oberman <rkoberman at gmail.com> writes:
>
> > Linking CXX executable ../bin/kfilemetadatareader
> > cd /usr/ports/x11/kdelibs4/work/.build/kio && /usr/local/bin/cmake -E
> > cmake_link_script CMakeFiles/kfilemetadatareader.dir/link.txt --verbose=1
> > /usr/local/bin/c++   -O2 -pipe -fno-strict-aliasing -Wnon-virtual-dtor
> > -Wno-long-long -Wundef -Wcast-align -Wchar-subscripts -Wall -W
> > -Wpointer-arith -Wformat-security -fno-exceptions -DQT_NO_EXCEPTIONS
> > -fno-check-new -fno-common -Woverloaded-virtual -O2 -DNDEBUG
> > -DQT_NO_DEBUG   -Wl,-rpath,/usr/lib:/usr/local/lib
> > CMakeFiles/kfilemetadatareader.dir/kfilemetadatareader_automoc.o
> > CMakeFiles/kfilemetadatareader.dir/kfile/kfilemetadatareaderprocess.o  -o
> > ../bin/kfilemetadatareader  ../lib/libkio.so.5.12.2
> > ../lib/libnepomuk.so.4.12.2 ../lib/libnepomukutils.so.4.12.2
> > /usr/local/lib/qt4/libQtNetwork.so /usr/local/lib/qt4/libQtXml.so
> > ../lib/libnepomuk.so.4.12.2 ../lib/libkdeui.so.5.12.2
> > /usr/local/lib/qt4/libQtGui.so /usr/local/lib/qt4/libQtSvg.so
> > /usr/local/lib/libsoprano.so ../lib/libkdecore.so.5.12.2
> > /usr/local/lib/qt4/libQtDBus.so /usr/local/lib/qt4/libQtCore.so -pthread
> >
> -Wl,-rpath,/usr/ports/x11/kdelibs4/work/.build/lib:/usr/local/lib/qt4:/usr/local/lib:
> > -Wl,-rpath-link,/usr/ports/x11/kdelibs4/work/.build/lib
> > ../lib/libkio.so.5.12.2: undefined reference to
> > `Strigi::AnalysisResult::AnalysisResult(std::basic_string<char,
> > std::char_traits<char>, std::allocator<char> > const&, long,
> > Strigi::IndexWriter&, Strigi::StreamAnalyzer&, std::basic_string<char,
> > std::char_traits<char>, std::allocator<char> > const&)'
> > collect2: ld returned 1 exit status
>
> This looks like libc++ and libstdc++ being mixed when building your C++
> ports.
>

OK. I believe that this implies that there are libraries linked to both
libraries. Correct? I have not seen this with any other C++ ports. How can
I track this down or work around this? I can't see how anything it links to
be linked to stdlibc++, but  I'm looking.I think there are aaout 68
sharables linked to the prior version.

Or do I simply not understand the issue?
-- 
R. Kevin Oberman, Network Engineer, Retired
E-mail: rkoberman at gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-freebsd/attachments/20140305/10a82065/attachment.html>