headers
Bill Ross | 28 May 2011 17:01
Picon
Favicon
Gravatar

CrossCompiling: error: 'lucene::analysis::standard' has not been declared

Been struggling with this for quite some time. No net search results, so I am doing something unique and / or stupid.

 

clucene-core-0.9.21b, strigi-0.7.2

 

Q: Is this the right version combo for KDE-4.6.1?

Q: has anyone gotten kde-buildrc script to cross-compile or hints how to do so?

Q: Are there some clucene config flags I may have missed to build classes 'lucene::analysis::standard`, 'lucene::store::FSDirectory'?

Q: Any clues how to proceed?

 

Code:

 

cd /home/rossb/OpenWrt/backfire/build_dir/target-i386_glibc-2.6.1/strigi-0.7.2/src/luceneindexer &&

/home/rossb/OpenWrt/backfire/staging_dir/toolchain-i386_gcc-4.1.2_glibc-2.6.1/usr/bin/i486-openwrt-linux-gnu-g++  

-Dclucene_EXPORTS -D_REENTRANT -DQT_GUI_LIB -DQT_CORE_LIB -DHAVE_CONFIG_H -DQT_NO_DEBUG -O2 -pipe -march=i486 -funit-at-a-time -fhonour-copts -D_UNICODE -D_CL_HAVE_GCC_ATOMIC_FUNCTIONS=1

-I/home/rossb/OpenWrt/backfire/build_dir/target-i386_glibc-2.6.1/strigi-0.7.2/src/streamanalyzer

-I/home/rossb/OpenWrt/backfire/staging_dir/target-i386_glibc-2.6.1/usr/include/CLucene -I/home/rossb/OpenWrt/backfire/staging_dir/target-i386_glibc-2.6.1/usr/include/CLucene/analysis/standard 

-I/home/rossb/OpenWrt/backfire/staging_dir/target-i386_glibc-2.6.1/usr/include

-I/home/rossb/OpenWrt/backfire/staging_dir/target-i386_glibc-2.6.1/include -I/home/rossb/OpenWrt/backfire/staging_dir/toolchain-i386_gcc-4.1.2_glibc-2.6.1/usr/include 

-Wnon-virtual-dtor -Wno-long-long -ansi -Wundef -Wcast-align -Wchar-subscripts -Wall -W -Wpointer-arith -Wformat-security -fno-check-new -fno-common -fexceptions -Wno-unused-parameter -fvisibility=hidden -fvisibility=default -DNDEBUG -fPIC

-I/home/rossb/OpenWrt/backfire/build_dir/target-i386_glibc-2.6.1/strigi-0.7.2/src/luceneindexer

-I/home/rossb/OpenWrt/backfire/build_dir/target-i386_glibc-2.6.1/qt-kde-2011-04-06/include

-I/home/rossb/OpenWrt/backfire/build_dir/target-i386_glibc-2.6.1/qt-kde-2011-04-06/include/QtGui

-I/home/rossb/OpenWrt/backfire/staging_dir/target-i386_glibc-2.6.1/usr/include/QtCore

-I/home/rossb/OpenWrt/backfire/build_dir/target-i386_glibc-2.6.1/strigi-0.7.2

-I/home/rossb/OpenWrt/backfire/build_dir/target-i386_glibc-2.6.1/strigi-0.7.2/src/streamanalyzer

-I/home/rossb/OpenWrt/backfire/build_dir/target-i386_glibc-2.6.1/strigi-0.7.2/src/streams

-I/home/rossb/OpenWrt/backfire/build_dir/target-i386_glibc-2.6.1/strigi-0.7.2/src/streams/strigi

-I/home/rossb/OpenWrt/backfire/staging_dir/target-i386_glibc-2.6.1/usr/include

-I/home/rossb/OpenWrt/backfire/staging_dir/toolchain-i386_gcc-4.1.2_glibc-2.6.1/usr/include  

-fPIC -o CMakeFiles/clucene.dir/cluceneindexmanager.cpp.o

-c /home/rossb/OpenWrt/backfire/build_dir/target-i386_glibc-2.6.1/strigi-0.7.2/src/luceneindexer/cluceneindexmanager.cpp

 

Errors…

/home/rossb/OpenWrt/backfire/build_dir/target-i386_glibc-2.6.1/strigi-0.7.2/src/luceneindexer/cluceneindexmanager.cpp:45: error: 'lucene::analysis::standard' has not been declared

/home/rossb/OpenWrt/backfire/build_dir/target-i386_glibc-2.6.1/strigi-0.7.2/src/luceneindexer/cluceneindexmanager.cpp:46: error: 'lucene::store::FSDirectory' has not been declared

…etc

 

I did the obvious of including StandardAnalyzer.h to cluceneindexmanager.cpp and adding include path. No change…

 

Thanks…

------------------------------------------------------------------------------
vRanger cuts backup time in half-while increasing security.
With the market-leading solution for virtual backup and recovery, 
you get blazing-fast, flexible, and affordable data protection.
Download your free trial now. 
http://p.sf.net/sfu/quest-d2dcopy1
_______________________________________________
Strigi-devel mailing list
Strigi-devel@...
https://lists.sourceforge.net/lists/listinfo/strigi-devel
Permalink | Reply | 1 comment |
headers
Egon Willighagen | 14 May 2011 16:51
Picon
Gravatar

Re: Is the project still alive?

Hi Raphael,

On Fri, Apr 15, 2011 at 5:19 AM, Raphael Kubo da Costa
<kubito@...> wrote:
> I see there are many bug reports around that have not been answered,
> there has been no release in quite some time (the kdepim folks are
> already resorting to hacks to make the next version work with strigi
> 0.7.2) and the mailing list has seen very little traffic recently.

There was some recent discussion about that.

> Please don't see this as a troll mail, I am really interested in knowing
> whether there is anyone acting as a project leader, if the bug reports
> are being looked at (crash reports are not the only kind of bug there)
> and if there is anyone involved in making a new release.

I guess people have been busy with life... :/

> My knowledge of strigi's internals are close to zero, but I can
> certainly help with buildsystem stuff and getting a new release out of
> the door.
>
> Is there anybody out there? :)

I am still here, and one of the people who worked on a chemistry
extension of Strigi, together with Alexander Goncearenco who worked on
that in a GSoc project... I have very little time for this project,
and Alexander picked up a PhD in Norway, and also had little time...
for the core team, I think they have had similar things...

Regarding the bugs... these often are from plugins, rather than the
core jstreams platform... the world is full of weird crap data,
requiring Strigi to be super robust... but also against 'use'...
recently there were bug reports caused by incomplete files send to
Strigi for analysis, causing plugins to crash because fields of
metadata ended in mid-air... :/

I'm sure this is not quite an answer you were hoping for, but like to
personally thank you for your patching and interest in the project...

Egon

--

-- 
Dr E.L. Willighagen
Postdoctoral Researcher
Institutet för miljömedicin
Karolinska Institutet (http://ki.se/imm)
Homepage: http://egonw.github.com/
LinkedIn: http://se.linkedin.com/in/egonw
Blog: http://chem-bla-ics.blogspot.com/
PubList: http://www.citeulike.org/user/egonw/tag/papers

------------------------------------------------------------------------------
Achieve unprecedented app performance and reliability
What every C/C++ and Fortran developer should know.
Learn how Intel has extended the reach of its next-generation tools
to help boost performance applications - inlcuding clusters.
http://p.sf.net/sfu/intel-dev2devmay
Permalink | Reply | 0 comments |

Gmane