On Thu, 5 Apr 2007, Collins, Andrew wrote:
Thanks for the quick reply. It looks like I do have the files, just not in
the right spot.
[EMAIL PROTECTED]:~$ sudo find / -name cni.h
/usr/include/c++/4.1.0/gcj/cni.h
This isn't where "GCJ_LIBDIR=$(GCJ_HOME)/$(LIBDIR_NAME)" should be pointing
is it?
$GCJ_LIBDIR is what gets passed to the linker with -L
I see you're using 4.1.0. I've never been able to get a sane gcj 4.1.0 on
Linux. The only time I've gotten a sane gcj 4.1.0 at all was on PPC Mac OS X
via darwinports.
On Linux, the only sane gcj 4.x binaries I've been able to build and use for
building PyLucene (all PyLucene tests run via 'make test' pass) were recent
gcj 4.2.0 snapshots.
To build PyLucene with gcj 4.x on Linux, the message at [1] can be relevant
too (starting from a source tarball is not working with gcj 4.x either, for a
reason I still don't know).
Andi..
[1]
http://lists.osafoundation.org/pipermail/pylucene-dev/2006-November/001404.html
_______________________________________________
pylucene-dev mailing list
[email protected]
http://lists.osafoundation.org/mailman/listinfo/pylucene-dev