On Fri, 4 Dec 2009, Sujan Shakya wrote:
PyLucene 3.0.0 worked for me as well in FreeBSD 7.0. So +1 vote from my
side.
But I needed to configure and change some paths.
In jcc/setup.py, the flags I added for FreeBSD are:
JDK = {
'freebsd7': '/usr/local/diablo-jdk1.6.0',
}
INCLUDES = {'freebsd7': ['%(freebsd7)s/include' %(JDK),
'%(freebsd7)s/include/freebsd' %(JDK)],
}
CFLAGS = {
'freebsd7': ['-fno-strict-aliasing', '-Wno-write-strings'],
}
DEBUG_CFLAGS = {
'freebsd7': ['-O0', '-g', '-DDEBUG'],
}
LFLAGS = {
'freebsd7': ['-L%(freebsd7)s/jre/lib/i386' %(JDK), '-ljava',
'-L%(freebsd7)s/jre/lib/i386/client' %(JDK), '-ljvm',
'-Wl,-rpath=%(freebsd7)s/jre/lib/i386:%(freebsd7)s/jre/lib/i386/server'
%(JDK)],
}
JAVAC = {
'freebsd7': ['javac'],
}
Shared object "libverify.so", required by "libjava.so", needs to be linked.
So, I add the following to /etc/rc.conf:
ldconfig -m /usr/local/diablo-jdk1.6.0/jre/lib/i386/
Thank you for the freebsd7 changes, I added to them jcc/setup.py on trunk.
There was a discrepancy between -rpath and -L in LFLAGS where you're using
client in one and server in the other. I opted for client but, of course,
that can be changed.
About requiring libverify.so, you might be able to get away with adding it
to the link line in LFLAGS as well so that you then don't have to play the
ldconfig -m trick. So I added -lverify into the LFLAGS.
Could you please try it out and see if you still need the ldconfig -m
treatment ? This is checked in to trunk rev 888682.
Thanks !
Andi..
