On 9/5/08, David Cournapeau <[EMAIL PROTECTED]> wrote:
> You should first test the binary (import numpy; numpy.test()), to see
> whether the built was really sucessful.
Hy again! :)
I've managed to build numpy and install it. 'import numpy' works OK,
numpy.show_config() looks OK, but when I try
Miroslav Sabljic wrote:
>
> Yes it looks so, but as this is first time I'm building numpy I wasn't
> sure. I will now experiment further and try to build it with MKL. Tnx
> for your help, I really appreciate it!
>
You should first test the binary (import numpy; numpy.test()), to see
whether the
On 9/5/08, David Cournapeau <[EMAIL PROTECTED]> wrote:
> This is not an error per se: fortran compiler is not mandatory. You will
> not get all the features of numpy, but you will get a working numpy
> without a fortran compiler. Looking at your build.log, it looks like it
> built successfully, no
Miroslav Sabljic wrote:
>
> The build log is in attachment. Now I just have to see about this
> error message I'm getting, "don't know how to compile Fortran code on
> platform 'nt'".
>
This is not an error per se: fortran compiler is not mandatory. You will
not get all the features of numpy, b
Miroslav Sabljic wrote:
>
>
> Thanks for the info. It would certanly be bad news for me if numpy
> really can't be build with VS 2008. I will try with numpy 1.1.1 and
> see what happens.
>
The code itself will have to be buildable with VS 2008 (if only because
of python 2.6, for which VS 2008 w
On 9/5/08, David Cournapeau <[EMAIL PROTECTED]> wrote:
> First, you are trying to build with numpy 1.0.2, which is really old.
> Update to a more recent version.
Yes, 1.0.2 is the version we are using on Linux so I went with that
one. I will try newer version.
> The error you are seeing may ind
Francesc Alted wrote:
>
> IIRC, Python 2.4 and 2.5 only supports the VS2003 of the MS series of
> compilers. With Python 2.6 and 3.0 I think that VS2008 will be the one
> supported.
>
Yes, but that's just stupid when you think about it. I mean, the python
code to deal with VS 2008 is there,
A Friday 05 September 2008, David Cournapeau escrigué:
> Matthieu Brucher wrote:
> > You may be right, I remember that VS2003 is hardcoded in some
> > places in distutils. I think I ran into this issue some months ago
> > as well.
>
> Mmmh, wonder if I could get around that in numscons :)
IIRC, Py
Matthieu Brucher wrote:
>
> You may be right, I remember that VS2003 is hardcoded in some places
> in distutils. I think I ran into this issue some months ago as well.
>
Mmmh, wonder if I could get around that in numscons :)
cheers,
David
___
Numpy-
> The error you are seeing may indicate that it is not possible to build
> python 2.5 extensions with VS 2008 with distutils (the message says
> distutils did not detect VS 2008 installation, and that may well be
> caused by distutils not knowing how to deal with VS 2008).
You may be right, I reme
Miroslav Sabljic wrote:
>
> I have tried building it with empty site.cfg file as you told me. The
> log file is in attachment.
>
>
First, you are trying to build with numpy 1.0.2, which is really old.
Update to a more recent version.
The error you are seeing may indicate that it is not possibl
On 9/4/08, David Cournapeau <[EMAIL PROTECTED]> wrote:
> On windows, if you only build numpy, you only need a C compiler, so in
> theory, python setup.py build, with an empty site.cfg, should work.
> But VS 2008 is significantly different from VS 2003, which is the most
> often used MS compiler to
> Sorry for this misapprehension! I meant to say that I'm building 32-bit
> numpy for 32-bit Python. The machine I'm using to build it is 64-bit
> Windows which has both 32-bit and 64-bit compilers and libraries
> installed. For now I'm doing only 32-bit builds.
>
> Tomorrow I will try to build num
David Cournapeau wrote:
> From scipy.org ? If you understood you have to use the MLK, then we
> have to improve the documentation (the installation pages are a mess
> ATM). It is certainly no mandatory.
Yeah, from scipy.org.
> Do you have to use VS 2008 ? Building python on windows is not easy
On Fri, Sep 5, 2008 at 2:30 AM, Miroslav Sabljić <[EMAIL PROTECTED]> wrote:
> David Cournapeau wrote:
>
>> Ok, you are building on windows, with a custom python, on windows 64
>> bits, with MKL... That's a lot at the same time.
>
> I'm building it with custom Python (built with VS 2008) on Win32. I
David Cournapeau wrote:
> Ok, you are building on windows, with a custom python, on windows 64
> bits, with MKL... That's a lot at the same time.
I'm building it with custom Python (built with VS 2008) on Win32. It is
a lot for me but I just have to do it and learn as much as posible
during the
Miroslav Sabljic wrote:
> Hy people!
>
> I'm quite a newbie regarding numpy so please excuse if I'm asking
> stupid questions.
>
No stupid question. Stupid answer may follow, though...
> I need to build Python and couple of his site-packages on Windows
> using Visual studio 2008. I've built Py
Hy people!
I'm quite a newbie regarding numpy so please excuse if I'm asking
stupid questions.
I need to build Python and couple of his site-packages on Windows
using Visual studio 2008. I've built Python 2.5.1 and now it's turn to
build numpy and I'm quite stuck because numpy build process is a
l
18 matches
Mail list logo
