On Tue, Dec 22, 2009 at 5:29 AM, Chris wrote:
> David Cournapeau gmail.com> writes:
>
>>
>> Ok, so the undefined functions all indicate that the most recently
>> implemented ones are not included. I really cannot see any other
>> explanation that having a discrepancy between the source tree, buil
On Mon, Dec 21, 2009 at 1:29 PM, Chris wrote:
> David Cournapeau gmail.com> writes:
>
> >
> > Ok, so the undefined functions all indicate that the most recently
> > implemented ones are not included. I really cannot see any other
> > explanation that having a discrepancy between the source tree,
David Cournapeau gmail.com> writes:
>
> Ok, so the undefined functions all indicate that the most recently
> implemented ones are not included. I really cannot see any other
> explanation that having a discrepancy between the source tree, build
> tree and installation. Sometimes, svn screw thing
Chris gmail.com> writes:
>
> By the way, I tried building 1.4rc1 and the same thing happens.
>
... however, I was am able to get a usable build from r7542. Not sure
how much more recent I can go before failures occurred. Somewhere
between 7543 and 7726.
__
David Cournapeau gmail.com> writes:
>
> Ok, so the undefined functions all indicate that the most recently
> implemented ones are not included. I really cannot see any other
> explanation that having a discrepancy between the source tree, build
> tree and installation. Sometimes, svn screw thing
David Cournapeau gmail.com> writes:
>
> Could you give us the generated config.h (somewhere in
> build/src.*/numpy/core/), just in case ?
>
Here it is:
http://files.me.com/fonnesbeck/d9eyxi
Thanks again.
cf
___
NumPy-Discussion mailing list
Num
On Mon, Dec 14, 2009 at 5:29 AM, Chris wrote:
> Chris gmail.com> writes:
>
>> Here it is:
>>
>> http://files.me.com/fonnesbeck/6ezhy5
>>
>
> Sorry, that link should be:
>
> http://files.me.com/fonnesbeck/qv8o59
Ok, so the undefined functions all indicate that the most recently
implemented ones a
Chris gmail.com> writes:
> Here it is:
>
> http://files.me.com/fonnesbeck/6ezhy5
>
Sorry, that link should be:
http://files.me.com/fonnesbeck/qv8o59
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinf
David Cournapeau gmail.com> writes:
> could you show the output from nm on umath.so, to check what
> symbols are missing. Maybe seeing the whole list would bring
> something.
Here it is:
http://files.me.com/fonnesbeck/6ezhy5
The symbol in question is in there, but I see that it does not
have
On Sun, Dec 13, 2009 at 12:55 PM, Robert Kern wrote:
>> I don't see any build error on this log ?
>
> See earlier in the thread. The error occurs at runtime:
Right.
Chris, could you show the output from nm on umath.so, to check what
symbols are missing. Maybe seeing the whole list would bring
s
On Sun, Dec 13, 2009 at 00:37, David Cournapeau wrote:
> On Sun, Dec 13, 2009 at 4:27 AM, Chris wrote:
>> Here is a log form a build of svn rev 7996 with no LDFLAGS specified, as
>> recommended by Robert. The result is the same, however.
>>
>> http://files.me.com/fonnesbeck/y7e9v2
>
> I don't see
On Sun, Dec 13, 2009 at 4:27 AM, Chris wrote:
> Here is a log form a build of svn rev 7996 with no LDFLAGS specified, as
> recommended by Robert. The result is the same, however.
>
> http://files.me.com/fonnesbeck/y7e9v2
I don't see any build error on this log ?
David
___
Here is a log form a build of svn rev 7996 with no LDFLAGS specified, as
recommended by Robert. The result is the same, however.
http://files.me.com/fonnesbeck/y7e9v2
cf
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.or
Chris gmail.com> writes:
>
> Charles R Harris gmail.com> writes:
> >
> > Maybe there is a stray old file floating about somewhere.
> Chris, is there a locate command for the mac? Could you track
> down numpy related files and make sure none are sitting in some
> dusty old corner?Chuck
Add
Charles R Harris gmail.com> writes:
>
> Maybe there is a stray old file floating about somewhere.
Chris, is there a locate command for the mac? Could you track
down numpy related files and make sure none are sitting in some
dusty old corner?Chuck
>
>
Sorry to be a pain on this, but it has
On Sat, Nov 28, 2009 at 6:44 PM, David Cournapeau wrote:
> On Sun, Nov 29, 2009 at 10:02 AM, Chris wrote:
> > Chris gmail.com> writes:
> >> Nothing looks out of order, but I still get the
> >> Symbol not found: _npy_cexp
> >> errors.
> >>
> >
> > This problem still persists through rev 7803. Is
On Sun, Nov 29, 2009 at 10:02 AM, Chris wrote:
> Chris gmail.com> writes:
>> Nothing looks out of order, but I still get the
>> Symbol not found: _npy_cexp
>> errors.
>>
>
> This problem still persists through rev 7803. Is there no solution
> for this?
The problem is that I don't see this issue
Chris gmail.com> writes:
> Nothing looks out of order, but I still get the
> Symbol not found: _npy_cexp
> errors.
>
This problem still persists through rev 7803. Is there no solution
for this? I have no clue where its coming from.
Thanks in advance.
_
David Cournapeau gmail.com> writes:
> 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 ?
>
Not that I ca
On Fri, Nov 13, 2009 at 4:56 AM, Chris wrote:
> David Cournapeau gmail.com> writes:
>
>>
>> On Thu, Nov 12, 2009 at 6:57 AM, Chris 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 tr
David Cournapeau gmail.com> writes:
>
> On Thu, Nov 12, 2009 at 6:57 AM, Chris 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 c
On Thu, Nov 12, 2009 at 6:57 AM, Chris 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.
David Cournapeau ar.media.kyoto-u.ac.jp> writes:
>
> Did you make sure to build from scratch and clean the working directory
> first ?
>
> I don't see the error on my macbook: umath.so has npy_cexp* functions
> defined.
>
> David
>
Just now tried deleting everything and pulling down numpy aga
David Cournapeau ar.media.kyoto-u.ac.jp> writes:
> Did you make sure to build from scratch and clean the working directory
> first ?
>
> I don't see the error on my macbook: umath.so has npy_cexp* functions
> defined.
>
> David
>
Yeah, here is my build script -- it removes the build directory
Chris wrote:
> I am building Numpy on OSX 10.6 using a recent update
> from SVN (r7726). Though I was able to build the package
> successfully, the resulting package generates an ImportError:
>
> import umath
> ImportError: dlopen(/Library/Python/2.6/site-packages/
> numpy-1.4.0.dev7726-py2.6-m
I am building Numpy on OSX 10.6 using a recent update
from SVN (r7726). Though I was able to build the package
successfully, the resulting package generates an ImportError:
import umath
ImportError: dlopen(/Library/Python/2.6/site-packages/
numpy-1.4.0.dev7726-py2.6-macosx-10.6-
universal.egg/
26 matches
Mail list logo
