#30 Soprano 2.8 cmake config problem: Virtuoso storage backend (missing libiodbc)

[pierrelud]

cmake config output:

-- Soprano Components that will be built:

• Redland storage backend
• Sesame2 storage backend (java-based)
• Raptor RDF parser
  (including TriG parser)
• Raptor RDF serializer
• The CLucene-based full-text search index library
• D-Bus server/client support

-- Soprano Components that will NOT be built:

• Virtuoso storage backend (missing libiodbc - http://www.iodbc.org)

Next step I take is to make ready to install this "missing libiodbc" and run into an obsoletes problem:

YaST2 conflicts list - generated 2012-09-24 15:35:01

installed unixODBC-devel-2.2.12-217.1.2.i586 obsoletes libiodbc-devel provided by libiodbc-devel-3.52.7-27.1.i586

[ ] deinstallation of unixODBC-devel-2.2.12-217.1.2.i586
[ ] do not install libiodbc-devel-3.52.7-27.1.i586

YaST2 conflicts list END

I do not want to uninstall "unixODBC-devel" for an obsolete "libiodbc-devel". How did you build Soprano 2.8?

[pierrelud]

How exactly did you build Soprano 2.8 not running into my problem?

(Can't use available binary because of this issue - http://sourceforge.net/p/soprano/bugs/31/)

[pierrelud]

refs:

http://forums.freebsd.org/showthread.php?t=15256

http://lists.debian.org/debian-qt-kde/2012/03/msg00058.html

http://trueg.wordpress.com/2011/09/22/about-strigi-soprano-virtuoso-clucene-and-libstreamanalyzer/

[pierrelud]

I'm still have this problem of "conflicting libraries" trying cmake.

I'm building Soprano myself because of the "libclucene.so.0, needed by libsopranoindex.so, not found" problem where I need to workaround and set SOPRANO_DISABLE_LUCENE_INDEX=1 in cmake config.

Anything I can do to build Soprano 2.8?

[Sebastian Trueg]

This is not a bug. It is a support request. Please do not use the bug tracker for this bug the mailing list.
As for your problem:

• If you are building for KDE you do not need clucene at all.
• I do nto know how Suse manages the packge problems with unixodbc and iodbc. Soprano still requires iodbc. That is something that should be fixed at some point...

[pierrelud]

Thanks for the reply, but I have to say I still do not know how to compile Soprano now. Unfortunately I'm using Soprano and Nepomuk in my application and if things does not work how can I develop application using Nepomuk. If there are no resolve or a knowledge base for problems how should the Nepomuk user base grow in the bigger scheme of things?

This was stated as a problem, not a bug, hence the appropriate heading/subject. This is not just a Suse problem but coming up in loads of other Distros. I also know that this is hard because this type of thing is a lot of time a problem in Linux with other libraries too, but I was after information to resolve this problem, help, not blaming Soprano, it might be beneficial to others later on.

[Sebastian Trueg]

I do not know how to solve this on Suse, except for maybe manually installing libiodbc i /usr/local. Distributions handle these things differently. I recommend you log into the #nepomuk-kde IRC channel or write to the nepomuk@kde.org mailing list. Those are better places to get help than the bug tracker.