Andi Vajda wrote:
On Mar 12, 2009, at 12:40, Michael McCandless <luc...@mikemccandless.com
> wrote:
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 so I got -F added in JCC's setup.py, but then when I built
pylucene,
it also needed the -F but I couldn't figure out where to add it?
No you don't. The flags you built JCC with are remembered and reused
by JCC to build your extensions. This is what this thread about
config.py is about.
Weird, that was not what I was seeing.
I think I cd'd to jcc, added -F into setup.py, "rm -r build", python
(coming from the right framework) setup.py build (confirmed -F
worked), sudo python setup.py install, cd .., make clean, make, and I
didn't see the -F flag on that g++ line.
Hmmm.... maybe somehow I was getting an older JCC install (in the
wrong framework) when running that make.
Let me go try it again (now that I've nuked the wrong framework).
Mike
