Share

Strigi

Code

Programming Languages: C++

License: GNU Library or Lesser General Public License (LGPL)

Repositories

browse code

Anonymous access: svn://anonsvn.kde.org/home/kde/trunk/playground/base/strigi Developer access: svn+ssh://$username@svn.kde.org/home/kde/trunk/playground/base/strigi

browse code, statistics, last commit on 2006-06-26 cvs -d:pserver:anonymous@strigi.cvs.sourceforge.net:/cvsroot/strigi login

cvs -z3 -d:pserver:anonymous@strigi.cvs.sourceforge.net:/cvsroot/strigi co -P modulename

Show:

What's happening?

  • strigi-0.6.3 (0.6.4) compilation failure

    when i compile 0.6.3/0.6.4, get some error; error message say's "stderr" and "fprintf" is not define . i check the file "strigithread.cpp" and add a include "include ", after that ,compileing i s ok! =============================================================== ... ... Scanning dependencies of target strigidaemon [ 71%] Building CXX object...

    2009-10-17 10:44:19 UTC by nobody

  • Comment: Solaris: linking fails due to relocations

    I've got a better idea for the patch. Look at how solaris / gcc is being checked in ./kdesupport/qimageblitz/blitz/CMakeLists.txt: if (NOT CMAKE_COMPILER_IS_GNUCXX AND CMAKE_SYSTEM_NAME MATCHES SunOS) target_link_libraries(qimageblitz -lm -lsunmath) endif (NOT CMAKE_COMPILER_IS_GNUCXX AND CMAKE_SYSTEM_NAME MATCHES SunOS) I think you should also just include "NOT...

    2009-10-02 00:05:44 UTC by thorstenhirsch

  • Comment: Solaris: linking fails due to relocations

    Hooray, I got it! I'll attach a patch.

    2009-10-01 23:01:45 UTC by thorstenhirsch

  • Comment: Solaris: linking fails due to relocations

    A guy in #opensolaris told me, that it looks as if the linker doesn't include the correct library paths, because even the basic functions fopen, fprintf, ... are listed. And in the kdesupport/strigi/src/streamanalyzer/CmakeLists.txt are a lot of lines that could mean what lib pathes to use ...sorry, i have no idea what these lines really mean. Please have a look into the CMakeListst.txt.

    2009-09-30 11:29:34 UTC by thorstenhirsch

  • Solaris: linking fails due to relocations

    Compiling strigi on OpenSolaris with gcc 3.4.2 leads to a lot of "relocations remain against allocatable but non-writable sections" error. I've attached the full output. I'm not sure what the error is about, seems like it has something to do with position-independent code as you can see here: http://docsun.cites.uiuc.edu/sun_docs/C/solaris_9/SUNWdev/LLM/p24.html OpenSolaris snv_123 / 32bit /...

    2009-09-29 23:29:30 UTC by thorstenhirsch

  • Comment: Build failure MacOS X 0.6.3 and 0.6.4

    I've written a simple patch http://bugsfiles.kde.org/attachment.cgi?id=37070 It doesn't seem like the best solution, but it looks like a fix to a previously half solved workaround.

    2009-09-19 18:30:52 UTC by nobody

  • Comment: Build failure MacOS X 0.6.3 and 0.6.4

    This happens with the latest version in the trunk too (r1017128)

    2009-09-19 16:24:40 UTC by nobody

  • Build failure MacOS X 0.6.3 and 0.6.4

    I get this when trying to compile strigi on Mac OS 10.6 (Snow Leopard). dbusmessagereader.cpp:66: error: prototype for ‘DBusMessageReader& DBusMessageReader::operator>>(int64_t&)’ does not match any in class ‘DBusMessageReader’ This happens on Mac OS X Snow Leopard using macports. Trying to build manually using version 0.6.4 has the same problem. dbus version:1.2.14_0 Any...

    2009-09-19 13:18:34 UTC by nobody

  • strigidaemon 0.7.0 segfault with broken png

    strigidaemon 0.7.0 gets a segmentation fault while it is reading a broken png-file. Output and stack trace (with gdb, filename "/some/file.png" changed): [...] Error in parsing: Keyword obj not found. Error: unexpected end of stream Error in parsing: Keyword obj not found. bad end in /some/file.png Program received signal SIGSEGV, Segmentation fault. [Switching to Thread...

    2009-09-02 01:35:21 UTC by toni_dietze

  • MpegEndAnalyzer does not respect the max. stream read length

    The MpegEndAnalyzer does not respect the maximum stream read length. This is problem especially in combination with all KDE applications that use KFileMetaInfo and expect a non-blocking behavior. Applications like Dolphin may freeze up to several seconds when hovering huge PDFs....

    2009-08-01 20:13:05 UTC by nobody

Our Numbers