[Numpy-discussion] Import error in builds of 7726

[David Cournapeau]

On Fri, Nov 13, 2009 at 4:56 AM, Chris <fonnesbeck at gmail.com> wrote:
> David Cournapeau <cournape <at> gmail.com> writes:
>
>>
>> On Thu, Nov 12, 2009 at 6:57 AM, Chris <fonnesbeck <at> gmail.com> wrote:
>>
>> >
>> > Yeah, here is my build script -- it removes the build directory entirely
>>
>> Ah, that's not enough. You need to clean the working tree as well. git
>> has the clean option for that, you can also use a quick script to do
>> this with parsing svn st output.
>
> I tried scrapping the whole directory and starting again. Same thing though.
> I do notice a bunch of configtest warnings though:
>
> gcc-4.2: _configtest.c
> _configtest.c:4: warning: function declaration isn’t a prototype
> _configtest.c: In function ‘main’:
> _configtest.c:5: error: size of array ‘test_array’ is negative
> _configtest.c:4: warning: function declaration isn’t a prototype
> _configtest.c: In function ‘main’:
> _configtest.c:5: error: size of array ‘test_array’ is negative
> lipo: can't open input file: /var/folders/Cp/Cp1bvHSvFwuPM0
> 9XVxsVF++++TI/-Tmp-//ccO4OC35.out (No such file or directory)
> _configtest.c:4: warning: function declaration isn’t a prototype
> _configtest.c: In function ‘main’:
> _configtest.c:5: error: size of array ‘test_array’ is negative
> _configtest.c:4: warning: function declaration isn’t a prototype
> _configtest.c: In function ‘main’:
> _configtest.c:5: error: size of array ‘test_array’ is negative
> lipo: can't open input file: /var/folders/Cp/Cp1bvHSvFwuPM09XVx
> sVF++++TI/-Tmp-//ccO4OC35.out (No such file or directory)
> C compiler: gcc-4.2 -DNDEBUG -g -fwrapv -Os -Wall -Wstrict-prototypes
> -arch i386 -arch x86_64 -pipe
>
> Not sure this has anything to do with it.

No, this is expected - those are related to size check, and
compilation failure is part of the process. Unfortunately, the output
of those checks is not easy to control.

I am afraid I don't see where the problem may come from. I used the
exact same build script as you, on the same version of mac os x, and I
don't see the problem. Is there anything non standard in your
environment that you can think of ?

David