Andi Vajda wrote:
On Thu, 12 Mar 2009, Michael McCandless wrote:
Anyway, finally, a little bruised from the whole process, and
wondering what other Python things on my Mac may now be broken... I
was able to run the tests successfully!
Do not pollute your env with soft links. Use -F instead. Really.
OK, I'll test with -F/... instead of symlink.
But why do I have two separate 2.5 Python installs, compiled w/
different options, in the first place? It's weird and I'd like to fix
it, I think (outside of building PyLucene, for my own sanity).
Maybe it's ambitious... but I'd really love a "for the impatient...",
in INSTALL, like this:
pushd jcc
<edit setup.py to configure for your env>
python setup.py build
sudo python setup.py install
popd
<edit Makefile to configure for your env>
make
sudo make install
make test
Normally, this is all that's needed. But you're making the two
manual edit steps smaller in importance than they really are. Still,
adding such a paragraph to the docs can't hurt.
Yeah true. It'd be good to have a place (wiki maybe) where we call
can put our "interesting flags we had to add" in each of those steps,
for different platforms, and then reference those places in the above
for-the-impatient instructions.
I assume warnings like this are OK on OS X?:
Warning: renaming static method 'toString' on class java.lang.Long
to 'toString_' since it is shadowed by non-static method of same
name.
This is not specific to OS X but specific to that Java class and
Python's inability to have static and non static methods named the
same.
OK makes sense.
and also these ones?:
cc1plus: warning: command line option "-Wstrict-prototypes" is
valid for C/ObjC but not for C++
That's noise from gcc caused by distutils/setuptools not
understanding C++ too well and passing it flags it shouldn't.
OK.
Mike
