lucene-pylucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sujan Shakya <suzan.sha...@gmail.com>
Subject Re: [VOTE] Release PyLucene 3.0.0-1 (rc2) (nag)
Date Fri, 04 Dec 2009 07:22:17 GMT
Hi, PyLucene users,

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/

Then in Makefile, I needed to do one change:

PREFIX_PYTHON=/usr/local (instead of /usr)

Then instead of make, I needed to run:

gmake
sudo gmake install
sudo gmake test

With all these, I could run pylucene well.

I hope these changes be added in the next release version so that other
FreeBSD users have very less to configure.

Thanks

/suzan

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message