Bug 748196

Which app fails to build?

Fwiw, we build clucene with option
  -DLUCENE_SYS_INCLUDES:PATH=%{_libdir}
because these (like clucene-core.h are not multilib-safe), so it ends up @
%{_libdir}/CLucene/clucene-config.h


Fwiw,
pkg-config --cflags libclucene-core
-I/usr/include/CLucene/ext  

fails to include -I%{_libdir}, so there's at least one upstreamable-bugfix to apply here.

(In reply to comment #1)
> Which app fails to build?

libsword from svn.  It now has support for detecting both 0.9 and 2.x CLucene versions and compiling against either, but a simple include of CLucene.h ends up trying to include CLucene/StdHeader.h, which tries to include CLucene/clucene-config.h, which doesn't exist.  I couldn't find this file anywhere under /usr/include/CLucene.h

find /usr/include/CLucene/ -name clucene-config.h -print

returns nothing.

Hope this is helpful.

> 
> Fwiw, we build clucene with option
>   -DLUCENE_SYS_INCLUDES:PATH=%{_libdir}
> because these (like clucene-core.h are not multilib-safe), so it ends up @
> %{_libdir}/CLucene/clucene-config.h
> 
> 
> Fwiw,
> pkg-config --cflags libclucene-core
> -I/usr/include/CLucene/ext  
> 
> fails to include -I%{_libdir}, so there's at least one upstreamable-bugfix to
> apply here.

(In reply to comment #2)
> (In reply to comment #1)

> > Fwiw, we build clucene with option
> >   -DLUCENE_SYS_INCLUDES:PATH=%{_libdir}
> > because these (like clucene-core.h are not multilib-safe), so it ends up @
> > %{_libdir}/CLucene/clucene-config.h

ah, reading your comment more closely, I understand.  
find /usr/lib64/CLucene/ -name clucene-config.h -print
/usr/lib64/CLucene/clucene-config.h

So, for now we can add a -I%{_libdir} to the clucene cflags

> > 
> > 
> > Fwiw,
> > pkg-config --cflags libclucene-core
> > -I/usr/include/CLucene/ext  
> > 
> > fails to include -I%{_libdir}, so there's at least one upstreamable-bugfix to
> > apply here.

%changelog
* Sun Oct 23 2011 Rex Dieter <rdieter> 2.3.3.4-3
- include LUCENE_SYS_INCLUDES in pkgconfig --cflags output (#748196)

Mind testing this build out?
http://koji.fedoraproject.org/koji/taskinfo?taskID=3493021

In the meantime, can you give me a hint where/how to checkout libsword svn for testing? (I suspect libsword may require patching)

OK, found it, http://www.crosswire.org/sword/develop/biblecs/svn.jsp

OK, from what I can gather, upstream cmake support "just-works", but the autotools support (pretty much) assumes
pkg-config --cflags libclucene-core
to work, per the patched build from comment #4

I'll issue an update shortly.

clucene-2.3.3.4-3.fc16 has been submitted as an update for Fedora 16.
https://admin.fedoraproject.org/updates/clucene-2.3.3.4-3.fc16

Dear Rex, sorry for not testing when you replied a week or so ago.  Been busy here.  I added a patch to libsword to handle the setup you told me about.  Have a look at the delta here:

svn log -r2666 http://crosswire.org/svn/sword/trunk
svn diff -r2665:2666 http://crosswire.org/svn/sword/trunk

But certainly agree that pkg-config -cflags should give the -I/usr/lib[64]

Thanks for doing this!

Package clucene-2.3.3.4-3.fc16:
* should fix your issue,
* was pushed to the Fedora 16 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing clucene-2.3.3.4-3.fc16'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2011-15988
then log in and leave karma (feedback).

clucene-2.3.3.4-3.fc16 has been pushed to the Fedora 16 stable repository.  If problems still persist, please make note of it in this bug report.