On Dec 12, 5:44 pm, Robert Kern wrote:
> On 2009-12-11 20:55 PM, hardcoreUFO wrote:
>
>
>
>
>
> > On Dec 11, 5:47 pm, Robert Kern wrote:
>
> >> Right, when the -lnpymath stuff got checked in. Looking at the build log
> >> you
> >> posted t
On Dec 12, 3:55 pm, hardcoreUFO wrote:
> Here is the log from a build without the LDFLAGS set. Having a quick
> look, all I can see are a few warnings and a CAPI version mismatch
> message. Any insight most appreciated. The build still gives the same
> umath error.
Sorry, forgot to
On Dec 11, 5:47 pm, Robert Kern wrote:
> Right, when the -lnpymath stuff got checked in. Looking at the build log you
> posted to numpy-discusson, it does appear that the $LDFLAGS is obliterating
> the
> intended flags. Please post a build log without setting those flags to
> numpy-discussion. A
On Dec 11, 12:29 pm, Robert Kern wrote:
> Don't specify LDFLAGS if you don't have to. It is obliterating the -l flag for
> the npy_math library that numpy builds internally and tries to link with.
Unfortunately, that did not eliminate the error. I thought it was
something that was changed in Nump
On Dec 11, 12:29 pm, Robert Kern wrote:
> On 2009-12-10 17:09 PM, hardcoreUFO wrote:
>
> > For the past several weeks, I have been unable to build numpy from
> > source, at least nothing that works. The issue is that symbols appear
> > to be missing from umath. When nump
For the past several weeks, I have been unable to build numpy from
source, at least nothing that works. The issue is that symbols appear
to be missing from umath. When numpy is imported, I get the following:
In [1]: import numpy
Tracebac
I have some code that I am trying to debug (Python 2.5.2 on OSX) using
pdb. However, when the code reaches the pdb.set_trace(), it does not
allow me to view the current line:
> /Users/chris/Research/ISEC/build/bdist.macosx-10.3-i386/egg/pyrl/reinforcement.py(943)__call__()
(Pdb) n
> /Users/chris/R
