Hi,
On Sat, Oct 25, 2014 at 11:26 PM, David Cournapeau wrote:
> Not exactly: if you build numpy with mingw (as is the official binary), you
> need to build everything that uses numpy C API with it.
Some of the interwebs appear to believe that the mingw .a file is
compatible with visual studio:
h
Not exactly: if you build numpy with mingw (as is the official binary), you
need to build everything that uses numpy C API with it.
On Sun, Oct 26, 2014 at 1:22 AM, Matthew Brett
wrote:
> On Sat, Oct 25, 2014 at 2:15 PM, Matthew Brett
> wrote:
> > On Fri, Oct 24, 2014 at 6:04 PM, Matthew Brett
On Sat, Oct 25, 2014 at 2:15 PM, Matthew Brett wrote:
> On Fri, Oct 24, 2014 at 6:04 PM, Matthew Brett
> wrote:
>> Hi,
>>
>> We (dipy developers) have a hit a new problem trying to use the
>> ``npy_log`` C function in our code.
>>
>> Specifically, on Linux, but not on Mac or Windows, we are gett
On Fri, Oct 24, 2014 at 6:04 PM, Matthew Brett wrote:
> Hi,
>
> We (dipy developers) have a hit a new problem trying to use the
> ``npy_log`` C function in our code.
>
> Specifically, on Linux, but not on Mac or Windows, we are getting
> errors of form:
>
> ImportError: /path/to/extension/distance
Hi,
We (dipy developers) have a hit a new problem trying to use the
``npy_log`` C function in our code.
Specifically, on Linux, but not on Mac or Windows, we are getting
errors of form:
ImportError: /path/to/extension/distances.cpython-34m.so: undefined
symbol: npy_log2
when compiling something
