[Numpy-discussion] Is there a known problem compiling numpy with VC7?

Travis Oliphant oliphant.travis at ieee.org
Mon Feb 6 22:14:01 CST 2006


Tim Hochberg wrote:

> Travis Oliphant wrote:
>
>> Tim Hochberg wrote:
>>
>>>
>>> Just a little update on this:
>>>
>>> It appears that all (or almost all) of the checks in 
>>> generate_config_h must be failing. I would guess from a missing 
>>> library or some such. I will investigate some more and see what I find.
>>>
>> That shouldn't be a big problem.  It just means that NumPy will 
>> provide the missing features instead of using the system functions. 
>> More problematic is the strange errors you are getting about void * 
>> not having a size.  The line numbers you show are where we have 
>> variable declarations like
>>
>> register intp i
>>
>> Is it possible that integers the size of void * cannot be placed in a 
>> register??
>
>
> OK, I think I found what causes the problem. What we have is lines like:
>
>        for(i=0; i<n; i++, ip+=skip, op+=oskip) {
>
> where op is declared (void*).

There shouldn't be anything like that.   These should all be char *.  
Where did you see these?

>
> Of course, unfuncmodule then failed to compile. A quick peak shows 
> that it's throwing a lot of syntax errors. It appears to happen 
> whenever there's a longdouble function defined. For example:
>
> longdouble sinl(longdouble x) {
>    return (longdouble) sin((double)x);
> }

On your platform longdouble should be equivalent to double, so I'm not 
sure why this would fail. 

-Travis






More information about the Numpy-discussion mailing list